System, Method, and Process for the Automatic Generation of Documents

ABSTRACT

The present invention is in the field of data correlation and automatic document generation. Specifically, the invention relates to a system that identifies and retrieves event information and personal information associated with a user, as well as agency information, including event-related agency information, to identify and automatically generate correlating documents, including documents like personalized legal petitions and contracts, that include agency information, event information, and/or personal information associated with a user.

CLAIM OF PRIORITY TO PRIOR APPLICATIONS

This application is a continuation-in-part of U.S. Non-Provisional patent application, Ser. No. 14/511,697, filed on Oct. 10, 2014, entitled “System, Method, and Process for the Automatic Generation of Documents,” which claims the benefit of the filing date of U.S. Provisional Application, Ser. No. 61/889,043, filed on Oct. 10, 2013, entitled “System, Method, and Process for the Automatic Generation of Documents.” The entire disclosures of U.S. Non-Provisional patent application, Ser. No. 14/511,697 and U.S. Provisional Application, Ser. No. 61/889,043, are hereby incorporated by reference into the present disclosure.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention is in the field of data correlation and automatic document generation. Specifically, the invention relates to a system that identifies and retrieves event information and personal information associated with a user, as well as agency information, including event-related agency information, to identify and automatically generate correlating documents, including documents like personalized legal petitions and contracts, that include agency information, event information, and/or personal information associated with a user.

SUMMARY OF THE INVENTION

The present invention is directed generally to data correlation and automatic document generation, and is directed more particularly to the collection, aggregation, and analysis of agency information, event-related agency information, personal information, and event information associated with a user, including arrest and case disposition information associated with a user, and the provision of aggregated public record information to be used for the automatic generation of related documents, and/or along with other data collected from secured third-party service providers, for use by a user to automatically generate documents.

Specifically, the invention is a system, process, and method for the automatic generation of documents that correlate with event and personal information associated with a user, and agency information, including event-related agency information. The system collects personal information associated with a user, possibly through a secured third-party service provider login that allows the system to authenticate a user upon login to the system.

Once a user is authenticated, the system collects event information associated with a user by receiving, through secured transfer or other means, event information from event information databases that correlate with personal information associated with a user. The system then correlates event information associated with a user with agency information, including event-related agency information that may be received, through secured transfer or other means, from agency information databases. The system may then determine if a user may benefit from a correlating document based on the correlation between event information associated with a user and event-related agency information. The system may assign values to event information in order for the event information to be used as variables in the system's algorithm(s) that correlates event information with event-related agency information. The system may then identify a document that may be of interest and/or beneficial to a user based on the correlation of agency information, event information, and personal information associated with a user. The system may then format the different kinds of information into a format that correlates with the format of a correlating document and places the information on data tables on a system database. Specific data fields within a data table correlate with numbered fields on a form used to generate a document. The form, once populated with the information from correlating data fields in a data table, is designed to generate a personalized document. The invention also correlates numbered fields in a document with relevant agency information to generate a document that correlates with agency information. A user of the system may be an attorney or an individual, hereinafter referred to as “user”, who is interested in drafting documents, including filing or responding to litigation with legal documents, by more efficiently drafting documents, including legal documents.

According to one general aspect, a method includes but is not limited to determining agency information and event information, and personal information, wherein the event information is related to a plurality of events, of which at least one event may be associated with an individual. The method further includes but is not limited to correlating the event and event-related agency information within the agency information and correlating the event-related agency information with a document and generating a document by correlating the various types of information with fields on a form that correlate with the information. A user may also select a document to be generated by the system. The system may then populate fields on a form with correlating information associated with a user and query a user for any remaining information required to populate the remainder of a form. The system may then correlate information entered by a user, with information, including event information, personal information, and event-related agency information, in order to identify user errors or suggest corrections or information for a particular field.

According to another general aspect, a system includes but is not limited to an acquisition system that is operable to determine agency information and event information wherein the event information is related to a specific event, of which at least one event is associated with a user, and a document generating system that is operable to correlate the event and event-related agency information within the agency information, with a correlating document, to generate a personalized document that is associated with a user and that complies with and/or includes personal information, event information, and/or event-related agency information .

According to another general aspect, a method includes but is not limited to correlating information, including personal and event information, associated with a user, with event-related agency information and assigning values to the event information to be entered into an algorithm that correlates event-related agency information with a correlating document that may benefit a user, and generating a correlating document that includes event information and event-related agency information in the correlating document.

According to another general aspect, a method includes determining agency information, determining an event from event information, the event being associated with a user, determining an inferred event from the event, based on a rule associated with the event, correlating the inferred event with inferred event-related agency information within the agency information, and correlating the event information and/or event-related agency information with a correlating document, and generating that document by populating fields on the document that correlate with event-related agency information, event information, and personal information associated with a user, that includes the inferred event-related agency information, and that complies with document-related agency information.

Many other objects, features, advantages, benefits, improvements, and non-obvious unique aspects of the present invention, as well as the prior problems, obstacles, limitations, and challenges that are addressed, will be evident to the reader who is skilled in the art, particularly when this application is considered in light of the prior art. It is intended that such objects, features, advantages, benefits, improvements, and non-obvious unique aspects are within the scope of the present invention; the scope of which is limited only by the claims of this and any related patent applications and any amendments thereto.

To the accomplishment of all the above, it should be recognized that this invention may be embodied in the form illustrated in the accompanying drawings, with attention being called to the fact, however, that the drawings are illustrative only, and that changes may be made in the specifics illustrated or described.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the invention may be obtained from the drawings as described in greater detail in the DETAILED DESCRIPTION OF PREFERRED EMBODIMENT section which follows:

FIG. 1A illustrates a system diagram of a system for data analysis and automatically generating documents and notifications.

FIG. 1B is a closer view of the agency information databases and event information databases in the system diagram in FIG. 1A.

FIG. 1C is a closer view of the Forms databases and Secured Third-party Service Providers Databases in the system diagram in FIG. 1A.

FIG. 2A illustrates an example of a screenshot of a user login screen.

FIG. 2B illustrates a secured third-party service provider authorization dialogue box.

FIG. 2C is an example of a personalized notification shown in FIG. 1A.

FIG. 3 is a flowchart system process for generating documents and/or notifications.

FIG. 4 is a flowchart of a system process for generating a petition for expunction.

FIG. 5 illustrates an example of an event record containing event information.

FIGS. 6A-6C are an illustration of an example data table on the system database that may be populated with event information associated with a user.

FIGS. 7A1-7A4 illustrate an example of the event information component of the algorithm.

FIG. 7B illustrates an example of the event-related agency information component of an algorithm

FIGS. 7C1-7C2 illustrate an example data table with messages and queries that the system may communicate to a user, based on the instructions of the algorithm in FIGS. 7A1-7A4 and 7B.

FIG. 8A illustrates an example of event-related agency information, Chapter 55 of the Texas Criminal Code.

FIGS. 8B1-8B2 illustrate an example of event-related agency information, Texas Criminal Justice Process.

FIGS. 8C1-8C2 illustrate an example of event-related agency information, data migration policy for a court clerk.

FIG. 8D illustrates an example of event-related agency information, a list of courts with contact information.

FIG. 8E illustrates an example of event-related agency information, a list of law enforcement agencies.

FIGS. 9A & 9B illustrate an example of an algorithm used by the system 10 to calculate the data migration of public records information.

FIG. 10A illustrates an example of a data table that contains data fields of event information and person information associated with a user.

FIG. 10B illustrates an example of a data table that contains data fields of event information associated with a user and event-related agency information.

FIG. 11A-FIG. 11E illustrate an example of form documents used to generate a petition for expunction.

FIG. 12A-FIG. 12E illustrate an example of a Petition for expunction generated by the system.

FIG. 13 is a flowchart of a system process for generating documents and/or notifications.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENT

FIG. 1A is a block diagram of a system 10 for automatically generating documents. In the example of FIG. 1A, the system 10 is operable to provide highly targeted and specialized documents and additional services 64, including the sending daily follow-up search queries to event information databases 34 to provide the user 12 with monitoring and analysis of event information 42 associated with a user 12 or the client(s) of a user 12. Examples of the types of event information databases 34 are illustrated in FIG. 1B.

The system 10 may be accessed by an individual, or agent of an individual, referred to hereafter as “user” 12, using a keyboard 14 attached, including wirelessly, to a computer 16 or mobile device 18 that is connected to the system 10, for example, over a network 20, such as the internet. A user 12 views and interacts with the system 10 through an interface 22 visible on the screen of the computer 16 or mobile device 18. The system 10 may be connected to a printer 68 or other device that may enhance a user's 12 experience and/or interactions with the system 10 and should be apparent to those familiar with the technology described.

The system 10 will prompt a user 12 to enter his username and password, shown in FIG. 2A to access the system 10. An individual may become a user 12 of the system 10 by typing in the individual's login information (e.g., username and password) for an active account with a secured third-party service provider 26 (e.g., such as Facebook, LinkedIn, Westlaw, Wolfram Alpha, etc.). A user 12 may also access the system 10 using a traditional sap account login 24 and log in directly to the system 10 without providing a user's 12 account login information to a secured third-party service provider 26.

If a user 12 elects to access the system 10 using the secured third-party service provider login 26, the system 10 calls out by secure connection to the API of the third-party service provider's database 28 using the account login information submitted by a user 12. Many secured third-party service providers allow other developers of systems, like the example system 10 in FIG. 1A, to call out to the third-party's web-based platforms 28 in order to provide the system 10 with personal information 30 associated with a user 12, when a user 12 authorizes the system 10 to do so, for example, by, providing the system 10 with a user's 12 login information to a secured third-party service provider account 26. The secured third-party service provider database 28 sends back personal information 30 associated with a user 12 and the system 10 receives this personal information 30 through the system's acquisition system 32.

The personal information 30 received from a secured third-party service provider database(s) 28 allows the system 10 to identify a user 12, without a user 12 experiencing the inconvenience of entering a user's 12 personal information 30. The system 10 benefits from safely and securely authenticating a user 12 through a secured third-party service provider login 26. The system 10 receives valuable personal information 30 associated with a user 12 that the system 10 may later correlate with other information; to suggest documents 46 and that may be beneficial to a user 12.

Looking to FIG. 2A, shown is an illustration of an example login screen, whereof would be visible to a user 12 on the interface 22 of their mobile device 18. A user 12 may login using the traditional sap system login 28 or choose to login in using a choice of secured third-party service provider login 26 options. In this example, Facebook and Linkedln are shown as third-part service providers, however the system 10 may be configured to allow a user 12 to enter login information to any variety of secured third-party service providers.

Once the system 10 identifies a user 12, the system 10 sends a search query by calling out over a secure connection to the API of event information databases 34 searching for event records 62 and/or event information 42 associated with a user 12. In the context of the current disclosure, “API” refers to Application Programming Interface. Event information databases 34 are databases that collect, aggregate, and/or otherwise possess event records 62 and/or event information 42 derived from event records 62.

Looking to FIG. 2B, shown is an illustration of a secured third-party service provider authorization dialogue box 210 visible to a user 12 who chooses to login to the system 10 through a secured third-party service provider login 26. The secured third-party service provider may request that a user 12 provide an additional approval before the secured third-party service provider agrees to send to the system 10 any personal information 30 associated with a user 12. The system 10 collects the personal information 30, in this example, from the secured third-party service provider database(s) 28, to identify a user 12 and to search for correlating event information 42 associated with a user 12. This personal information 30 may include, for example, the date of birth, full name 510, sex 514, and race 516, or geographic information 212 associated with a user 12, among other information, that a third-party service provider database(s) 28 may possess on their databases and are willing to share with the system 10.

The personal information 30 received from the secured third-party service provider database(s) 28 is a mechanism for the system 10 to identify a user 12 without a user 12 also experiencing the inconvenience of entering a user's 12 personal information 30. In addition, the system 10 benefits from a login mechanism that safely and securely authenticates a user 12 through a trusted secured third-party service provider (e.g., LinkedIn, Facebook, etc.). The system 10 collects valuable personal information 30 associated with a user 12 that the system 10 may later correlate with other information, including event information 42 and agency information 40, and to suggest and/or generate correlating documents 46 and additional services 64 that may be beneficial to a user 12.

Once the system 10 identifies a user 12, the system 10 sends a search query, by, for example, calling out over a secure connection to the API of event information databases 34, searching for event records 62 and/or event information 42 associated with a user 12 and/or according to other parameters found within the job data 48. The event information databases 34 respond to the search query by sending back to the system 10, event information 42 associated with a user 12. If event information 42 associated with a user 12 is located on event information databases 34, the acquisition system 32 receives the event information 42 associated with a user 12. The acquisition system 32 collects event information 42 (418) associated with a user 12 and uses a script to reformat specific event information 42 into the format of data fields 616 contained in data tables 618 on the system database 56.

Moving forward, the automatic document generating system 10 includes an acquisition system 32 that is operable to acquire information from event information databases 34 and agency information databases 36, Examples of event information databases 34 and agency information databases 36 are shown in FIG. 1B.

The acquisition system 32 may be operable to execute functions such as the following: download files from servers, download e-mail attachments, perform screen scraping (e.g., parsing Hyper-Text Transfer Protocol (HTML) code in web pages to mine desired patterns of content), employ the use of Optical Character Recognition (“OCR”) 38, or obtain personal information 30, or event information 42, associated with a user 12. For example, a software agent may be used to monitor event information 42 associated with a user 12, or another individual, and/or periodically download desired or pre-identified types of information therefrom. The system 10 may be configured to include Optical Character Recognition (“OCR”) technology 38 in the acquisition system 32 to identify and digitize information that may be relevant to a job or task of the system 10.

The acquisition system 32 may obtain useful information from other sources, including sources that are internal either to the automatic document generating system 10 or to a user 12. For example, the acquisition system 32 may obtain information from the service data 44, which refers generally to instructions for the system 10 to create a variety of correlating documents 46 that the system 10 may automatically generate for a user 12 when the system 10 identifies specific event information 42and/or personal information 30, associated with a user 12.

Furthermore, the acquisition system 32 also may be responsible for obtaining address or other information for assisting a user 12 in automatically generating documents 46. For example, the acquisition system 32 may identify relevant information in the user's 12 personal information 30 that was collected from secured third-party service provider databases 28 (e.g., LinkedIn, Facebook, or Westlaw, Wolfram Alpha, etc.). In another example, the acquisition system 32 may obtain address information 830 from agency information 40 to format a correlated document 46, and/or to deliver the document 46 to the proper location, and/or to enter the agency's address 830 in a correlating document 46 (e.g., the petition for expunction example below includes agency contact information 122).

In other implementations, the acquisition system 32 may use an identification of a user 12 derived from personal information 30 received from secured third-party service provider database(s) 28 and/or an event record 62, and/or may use other known techniques for obtaining address or other contact information for a user 12 (e.g., on-line phone books or background check services). In the latter case, the automatic document generating system 10 may not be able to ascertain an identity or contact information for a user 12 with any certainty, and ultimately may send information not only to a user 12, but also to other users 10 determined by the acquisition system 32 (e.g., users with a same or similar name as a user 12).

Information associated with an instruction, operation, and/or result(s) of the acquisition system 32 may be provided in, or in conjunction with, job data 48. That is, the term job in this context may refer to an internal device or storage scheme for managing and tracking requirements of a user 12 (e.g., with respect to generating a particular document 46 or for correlating information associated with a document). For example, a user 12 may be interested in generating a unique document 46 that contains information about a particular event. That is, the document 46 may include a document 46 that may also indicate desired types of event-related agency information 40, personal information 30, and/or event information 42 that is desired by a user 12, or the recipient of a user's 12 document 46, and presented in a particular format, or for a particular purpose, (e.g., in order to comply with statutes and/or court rules found in agency information).

For example, the job data 48 may specify a type of the agency information 40 that is desired, and/or event information 42 that is relevant in determining whether a correlating document 46 is available for a user 12. Of course, it should be understood that the term job or job data 48 is intended to represent one or more jobs or job data 48, so that a system 10 generating a document 46 may contain a plurality of j obs, where each such job or job data 48 is associated with one or more of the correlating documents 46 being generated by the system 10.

For example, the job data 48 may include, or be associated with, a first table of one or more relational databases that stores the user's 12 personal information 30, a second table that stores event information 42 acquired by the acquisition system 32 from the user's 12 event information 42 in response to requirements of a specific job of the job data 48, and a third table that stored event-related agency information 40 (316) acquired from the agency information 40, also in response to a job of the job data 48. That is, the acquisition system 32 may be responsible for obtaining relatively large sets of information from the agency information 40 and/or the event information 42. Elements of agency information 40 may be related to a user's 12 event information 42. Inversely, elements of a user's 12 event information may be related to agency information 40. Therefore, it may be unnecessarily duplicative to store discrete datasets in which an event record 62 is associated with its corresponding event-related agency information 40. With the teachings of the current disclosure, the information may be stored in separate tables and aggregated when needed or desired by the automatic document generating system 10 for generating documents 46 for the user 12, and/or the lawyer or law firm for the benefit of the user 12.

Referencing FIG. 1A, the notification system 59 may determine an identity and/or contact information for the user 12, (i.e., for all users 12 involved who have created a user 12 profile and/or a user 12 chooses (324) a document after logging in through a secured third-party provider). The notification system 59 may then send a notification 52 to the user 12, (342) (e.g., by e-mail, and/or in a text message or phone call). Once a user 12 creates a profile or accesses the system 10 through a secured third-party service provider login 26 and requests to receive notifications 52. The notification 52 may identify that a lawsuit was filed against the user 12, or against a client of the user 12, and provide options for a user 12 to learn more about the charges and other parties to the lawsuit. In an embodiment contemplated by the inventor, the notification 52 would arrive as an e-mail or text message to the user's 12 mobile device 18, or computer 16 connected to a network 20 in the form 60 of an easy-to-read case summary 216 that may include a respond button 214, as shown in FIG. 2C. A user 12 may also choose to press the respond button 214 and the system 10 automatically begins generating a document 46 that responds to the charges. The system 10 queries event information databases 34 for any new court filings (340) that match the personal information 30 associated with the user 12, and then automatically send a user 12 a notification 52. The case summary is accomplished by identifying the type of filing that is entered against a user 12 and then identifying the content of the document(s) 46 filed against the user 12, possibly using OCR 38 or some other method, to determine the contents of the information in a document(s) 46. The system 10 will then source the event-related agency information 40 needed to respond to the charges and select a form 60 from the forms database 58 that correlates to the event information 42 and/or event-related agency information 40 contained (338) in the charges or suit filed. The system 10 will automatically generate the document(s) 46 to include the information associated with the charges or suit filed against a user 12 (or user's 12 client), including the plaintiff(s), court name, and any procedural requirements associated with a document 46 of this type. The system 10 will query a user 12 to select from a list of options to populate on any remaining fields (326) on the document 46 that require the user's 12 input and/or selections (330) and that were not automatically populated by the system 10. A user 12 can make any further changes to the document(s) 46 and/or send the document(s) 46 directly from their mobile device 18 to the court through e-file 50 or send the document(s) 46 as an e-mail to another person, including a lawyer or law firm. The system 10 may also provide a user 12 with suggestions or options on how to respond based on the most common documents 46 filed by other similarly situated individuals or lawyers responding to similar charges and the effectiveness of the document(s) 46 utilized by these individuals in realizing a successful outcome with the response. The system 10 may provide a user 12 with statistics on the success rate of other individuals who faced similar charges in the same or a different jurisdiction by querying event information databases 34 for the event records 62 associated with individuals facing similar charges, and then identifying the correlating document(s) 46 that were generated by those other individuals to respond to the event records 62. The system 10 will analyze event records 62 to identify when a suit is filed against a user 12 and/or client of the user 12, and then send a notification 52 that includes the event information 42 associated with a user 12 or the user's 12 client.

The system 10 may also be configured for a user 12 to monitor legal activity or litigation against a user 12 and/or third party of interest. The notification(s) 52 based on event records 62 provides a user 12 with a variety of services that are, designed to increase the efficiency and awareness of a user 12 when generating documents 46 or identifying event records 62 associated with a user 12 or another individual.

The system 10 may be configured to provide reminders of filing deadlines for current lawsuits by correlating event records 62 associated with a user 12 (e.g., civil court filings) with event-related agency information 40 (e.g., Rules of Civil Procedure), to provide notifications 52 to the user 12 of approaching deadlines to a correlating document 46 that may and/or must be filed by a user 12. Notifications 52 may include, for example, suggestions of strategies and filings to consider based on the event records 62 associated with other individuals who faced the same or similar type lawsuit, in the same or a different court as the user 12. The system 10 correlates the event records 62 associated with a user 12 with the event-related agency information 40 to provide reminders of filing deadlines and to provide analysis of documents 46 or actions that other individuals selected in response to lawsuits with similar charges.

Civil case filings are examples of event information 42 that can be sourced by the system 10, in the manner described above, to identify event information 42 associated with a user 12 in order to provide a user 12 with the ability to respond to charges immediately by automatically generating documents 46 and/or forwarding notifications 52 from the system 10 directly to the user's 12 lawyer, in addition to other services provided by the system 10 for managing and/or responding to event records 62 associated with the user 12.

One example of a notification 52 from the system 10 to a user 12 is provided for illustrative purposes below in FIG. 2C. Even though FIG. 2C depicts a specific type of notification it should be understood that other notification 52 types could be implemented. FIG. 2C illustrates an example of a notification 52 that includes a case summary for a civil suit associate with a user 12. A user 12 also has the option to “respond” by automatically generating the relevant documents 46 associated with the event. Looking to FIG. 2C, the notification 52 may merely identify the filing of a lawsuit against a user 12, without providing the entire text of the event record 62 (e.g., case filing). In another instance, the notification 52 may include a notification 52 to a user 12 about an error the system 10 identified in the drafting of a document 46. To explain further, the system 10 can determine where the proper venue for a case filing or lawsuit should be by correlating the event information 42 with the event-related agency information 40 (e.g., by identifying the parties and subject matter of a particular lawsuit or document 46 and correlating this information to a particular field on a form 60 that is used by the system 10 to generate a correlating document). The system 10 may be configured to query event information databases 34 to determine if the court, where the lawsuit was filed, has personal jurisdiction over the parties in the subject matter suit and whether the suit is the type to allow the court to exercise subject matter jurisdiction over the case by correlating event information 42 contained in a particular field on a form 60 with event-related agency information 40. In this respect, the system 10 may provide a user 12 with a defense to the litigation against a user 12 if the system 10 identifies a flaw in the lawsuit based on a procedural error entered by the other party (e.g., by filing a case in the wrong court or not having personal jurisdiction over a defendant).

Another example of the described applications may be that a user 12 is seeking to become the Plaintiff in a case and is beginning to draft relevant documents 46, such as a petition. The system 10 will first verify names of parties, whereof are typically followed by LLC or Inc., etc. located within a particular field on a form 60 that requests this type of information (e.g., a field on a form 60 that contains the name of the other party). The system 10 is configured to determine if a user 12 correctly spelled the name of the company or corporation, and whether the type of business entity is properly identified based on corporate and other company filings (also considered event information 42) 110, including the entity's filings with the state or federal government. For example, a user 12 may utilize the system 10 to generate documents 46 such as a legal petition and accompanying documents 46, for filing a lawsuit against a trucking company, e.g., Jameson's Trucking of Tulsa, Okla. Once a user 12 enters the name of “Jameson's Trucking” in the appropriate field for the defendant's name, and “Tulsa, Okla.” in the field on a form 60 that requests the defendant's residence, the system 10 will query event information databases 34 to determine if Jameson's Trucking is a registered entity in Oklahoma, and if so, what type of entity. If the name is incorrectly spelled or the entity is incorrect (e.g., should be an LLC not an LLP), the system 10 will send a notification 52 to a user 12 identifying the error and/or automatically correct the error for the user 12. The system 10 may also perform a search of event information databases 34 to determine where a party to the suit is domiciled, if the party is suspected to be a resident of another state and assist a user 12 in determining where venue is proper by correlating the party associated event information 42 with event-related agency information 40. The system 10 may also be configured to, for example, automatically populate other fields on a form 60 that correlate to the event information 42 entered in another field on the form 60. For example, the system 10 may populate a field on a form 60 that requests the registered agent and principal place of business for a defendant that was entered earlier by the user 12 in response to a query by the system 10 to enter the defendant's name. This feature may also assist a user 12 with determining where to send a document 46 (e.g., in order to provide proper notice to the relevant parties to a document 46 or lawsuit).

If the system 10 identifies that a defendant is not an entity, but rather, an individual, the system 10 may be configured to perform a query of event information databases 34 for names that match the individual defendant's name to determine if any event information 42 associated with the defendant within the jurisdiction named in a form 60 to determine if the defendant's relationship with a jurisdiction may be sufficient to allow the court to exercise personal jurisdiction. Once the parties are identified, the system 10 may then automatically populate other fields on the form 60 that correlate to the event information 42 associated with the identified parties. In another example, the embodiment, presented below, determines the proper jurisdiction for filing a petition for expunction (as shown in FIGS. 12A-12E) of event information 42 associated with a user 12 based on where the events occurred in the event information 42 associated with a user 12, and correlating event-related agency information 40 that identify the proper jurisdiction for filing the petition for expunction (as shown in FIGS. 12A-12E) based on the particular event information 42 associated with a user 12.

The notification 52 may include suggestions on documents 46 or filings to consider based on the correlating documents 46 identified (322) as being associated with the event information 42 and/or agency information 40 associated with the user 12. The system 10 may also suggest documents 46 that were selected by other individuals who responded to similar documents 46 or filings, according to event information 42, including event records 62 such as court filings. The system 10 may also call out to third-party service providers to receive other information associated with a user 12 in order to suggest other documents 46 that are associated with issues identified in the event information 42 and that correlate with documents 46 and/or event-related agency information 40. The system 10 may then suggest the automatic generation of documents 46 that are beneficial to a user 12 based on the system's 10 analysis of the information associated with the user 12, the event, and/or the document 46 suggested by the system 10 and/or sought to be generated by the user 12. A user 12 may respond to the legal filing or suit, and/or begin the drafting of a response, by selecting from a list of documents 46 available and/or suggested by the system 10 that are already populated with the relevant event information 42 associated with the user 12. The names of the parties as well as the court name and the charges may be identified and sourced from the event information databases 34 and formatted into data fields 616 to correlate with a numbered field 1110 on the form(s) 60 used by the system 10 in automatically generating the correlating documents 46. A user 12 may now spend more time handling other aspects of their professions, such as courtroom strategy, by saving time during the generating of documents 46 and identifying needless errors in a document. Looking back to FIG. 1A, the event information databases 34 that host civil court filings are illustrated as providing the event information 42 to the system 10, which may be accomplished by calling out to the event information databases 34 using a secure connection and formatting the event information 42 associated with a user 12 in order to transmit a notification 52 that includes a case summary to the user's 12 mobile device 18, via text message or e-mail.

Then, a correlating document, also referred to as a legal document, may be generated by the system 10 for the user 12, for any of the above purposes or by using any of the techniques described herein, or other techniques. The document 46 (an example of which is illustrated in FIGS. 12A-12E) may thus include specific event information 42 associated with a user 12 and event-related agency information 40 that may be of particular use and interest to the user 12.

In this way, a user 12 may directly and/or indirectly benefit from the documents 46 that are of particular use and value to the user 12. For example, a user 12 may be an attorney that, with the described systems and tools of the current disclosure, is able to provide a service at a reduced cost; the service would otherwise, without the described systems and tools of the current disclosure, be more expensive due to the cost of generating or gathering documents 46 relevant to said service. Additionally, or alternatively, the document 46 generating system 10 provides a user 12 with an opportunity to provide further value through reduced costs and increased efficiency in generating documents 46 for the user 12.

By identifying event information 42 or agency information 40 that correlates to fields on a form 60 used to generate document(s) 46, the system 10 may source relevant information, identify documents 46 that may be generated with the information, and generate the document 46 automatically by matching the information to fields within the document 46 and/or to identify which document 46 correlates to the information. For example, the system 10 uses data from the user's 12 arrest records and/or case disposition records to determine if a user 12 meets the statutory requirements for filing a petition for expunction of event information 42. Once the system 10 determines whether or not the user's 12 event information 42 meets the statutory requirements for filing a petition for expunction, the system 10 uses the public records information, including the event information 42 and the event-related agency information 40 to populate the document 46 based on the specifications for filing a petition for expunction, as defined in the event-related agency information 40 records. Once the system 10 identifies that a user 12 meets the statutory requirements for filing a petition for expunction, the system 10 generates the documents 46 to be filed, the petition and order for expunction, among other correlating documents 46. The system 10 has the ability to correlate acquired public records information with relevant field(s)on the form 60, whereby, via said correlation, relevant field(s) (328) on form 60 are populated with the information from said acquired public records. The populated field(s) (328) on form 60, whereof are relevant to the acquired public records information, contain associated information that is formatted to coincide with the formatting of form 60. For any fields on the form 60 that remain unpopulated, the system 10 will query a user 12 to populate said unpopulated fields. The system 10 may also provide the user 12 with options for populating the remaining unpopulated fields. Said options are based on event information 42 or agency information 40 that correlates with a particular field. The system 10 will still provide options even if the information used to generate the options is not directly associated with the user 12.

The document 46 generating system 10 initially determines a job description. For example, a user 12 (a lawyer or law firm) may submit a request to the document 46 generating system 10, wherein the request may contain event-related information, legal issues, legal parameters, or other types of relevant information associated with a client. A job description is then generated based off the information included in the user's 12 request. To explain further, where the lawyer or law firm is a criminal defense attorney, the job description may utilize sections of the criminal code in which the lawyer or law firm finds helpful in providing services to the client.

The job description may specify a type or characteristic of desired agency information 40, as well as a type or characteristic of desired event information 42. In this regard, it should be understood that desired agency information 40 and event information 42 may be specified or described within the job description in the same, different, or overlapping manner(s). For example, a job description, both agency information 40 and event information 42 may be based on a user's 12 preference, an operation of the document 46 generating system 10, a format, or a storage/transmission protocol.

Furthermore, the job description may specify either the desired agency information 40 and/or the desired event information 42 with respect to one or more of the following: a statue, an ordinance, a law, a code section, a regulation, a rule, a municipality, a violation, a geographical region, or a judgment. For instance, a user 12 may draft a legal document whereof is based on information (referred to as agency information 40 in the context of the current disclosure) associated with a municipality's records; more specifically, it may not be obvious to the user 12 that the municipality's records contain an ordinance that prohibits actions of said municipality. In such cases, a user 12 may also not be aware of penalties associated with violating the local ordinance or with the municipality's specific requirements for drafting a particular legal document, the error notification 52 may be useful to a user 12 in identifying and/or correcting a drafting error that could result from such circumstances. The system 10 may accomplish this by querying event information 42 and agency information 40 databases to determine whether a user's 12 entry for a particular field or position of the form 60 used to generate the documents 46 complies with the correlating agency information 40 for the municipality, including event-related agency information 40, with the user's 12 entry for a particular field on a form.

The event information 42 may be queried according to a type of criminal offense or legal issue described therein, such as a type of criminal or civil suit, and/or based on a geographical region (e.g., whether a user 12 is drafting a legal document 46 for a jurisdiction in-state or out-of-state). The event information 42 also may be searched based on a period of time associated with the occurrence of the event(s). For example, the job description may request all of a certain type of event (e.g., arrests for a certain crime) that occurred in the last week or month.

The event information 42 and the agency information 40 may be determined according to a common parameter. For example, the job description may specify a regulation that is included in both the agency information 40 and event information 42.

In some implementations, the document 46 generating system 10 may be wholly or partially unique to the public records information. For example, as referenced above, sets of agency information 40 and sets of event information 42 may have formats, locations, and interfaces that are different from one another. As a result, it may be advantageous to configure the automatic document 46 generating system 10 to a particular type of agency/event information 42, prior to deployment for use by the user 12. For example, one implementation of the document 46 generating system 10 may be used in conjunction with Texas Criminal and/or Civil Code information, Illinois Criminal and/or Civil Code information, New York Criminal and/or Civil Code information, or the California Criminal and/or Civil Code information. In this way, components of the document 46 generating system 10 may be optimized for interactions with specific types or instances of the public records information.

In some implementations, the job description may merely specify desired event information 42, and the acquisition system 32 may include a rule engine for determining the types of agency information 40 that may be required, based on the event information 42. In other implementations, the agency information 40 may be downloaded virtually in whole for local storage/access (especially when the file size is relatively small; the downloaded agency information 40 may then later be queried based on specific event information 42 and/or the personal information 30). Still, in other implementations, the desired agency information 40 may be specified with more precision or detail, to minimize the difficulty of later queries processed against the specified agency information 40.

Based on the job description, agency information 40 may be determined and/or event information 42 may be determined. For example, desired types and/or instances of event information 42 may be downloaded from the event information 42 of the public records information, using information from the job description, such as just described. Similarly, data from the agency information 40 may be obtained in a manner specified by or for the user 12. In various implementations, either the desired agency information 40 or the desired event information 42 may be determined first, or, in other implementations, agency information 40 and event information 42 may be determined at the same or overlapping times.

FIG. 3 is a flowchart 300 illustrating an example operation of the system 10 shown in FIG. 1A. The automatic document generating system 10 is operable to correlate an event (as represented in the event record 62) with a subset of event related agency information 40 (i.e., event-related agency information 40). Conversely, the automatic document generating system 10 may correlate a selected subset of the agency information 40 with corresponding events of a plurality of the event records 62. The system 10 may also correlate the event record 62 associated with a user 12 and the agency information 40, including the event-related agency information 40, with a correlating document 46. The system 10 may generate a correlating document 46 that includes the personal information 30, agency information 40, including the event-related agency information 40, and/or event information 42 associated with a user 12. The document 46 will comply with and/or include the agency information 40 and event-related agency information 40.

The system 10 uses personal information 30 associated with a user 12 to identify and authenticate a user 12. The personal information 30 may also be used by the system 10 to locate event information 42 or event records 62 associated with a user 12 based on correlations with a user's 12 personal information 30. The personal information 30 is also used by the system 10 to populate documents 46 and/or identify correlating documents 46 for a user 12. This personal information 30 may include, for example, the date of birth, full name 510, sex 514, and race 516 associated with a user 12, among other information associated with a user 12 that third-party service provider database(s) 28 may possess on their databases, and of value to the system 10 in generating documents.

The event information databases 34 respond to the search query by sending to the system 10 any event information 42 associated with a user 12. If event information 42 associated with a user 12 is located on event information databases 34, the acquisition system 32 receives the event information 42 associated with a user 12 for further processing. The (314) acquisition system 32 identifies event information 42 associated with a user 12 and uses a script to reformat specific event information 42 into the format of the system database 56. Event information 42 associated with a user 12 is matched with a user's 12 personal information 30 and collectively stored on the system database 56. The system database 56 organizes event information 42 associated with a user 12, and personal information 30 associated with a user 12 in specific data fields 616 to be used by the system 10 to correlate with event-related agency information 40 and/or correlating documents 46 generated by the system 10 for a user 12.

If a correlation exists between the event information 42 and the event-related agency information 40, the system 10 determines if correlating documents 46 are also available that may also benefit a user 12. If a correlating document 46 is available, the system 10 may provide a user 12 with a correlating document 46 as an option, possibly among several other options of correlating documents 46 available to a user 12. A user 12 may select a correlating document 46 from the available correlating documents 46 according to the purpose, or benefit sought, of generating a particular correlating document 46 for a user 12. If, for example, a notification 52 of an event record 62 associated with a user 12 is a suspected instance of identity theft, a user 12 may login to the system 10 and learn more about the event information 42 associated with the notification 52. A user 12 may select a correlating document 46 that informs 60 the system 10 that a user 12 suspects an event record 62 is an instance of identity theft. The system 10 may then automatically generate correlating documents 46 for a user 12 that assist a user 12 in reporting the identity theft and correcting the event record 62 to remove a user's 12 personal information 30. The system 10 may automatically generate correlating documents 46 required for filing a lawsuit against an individual who misappropriated personal information 30 associated with a user 12. A user 12 may file the correlating documents 46 with the court clerk through e-file 50.

The (316) system 10 then sends a search query, or several search queries, for example, in the same manner described above, to agency information database 36 in order to collect event-related agency information 40 related to all or some of the event records 62 and/or event information 42 associated with a user 12. The system 10 receives event-related agency information 40 from agency information databases 36 through the acquisition system 32 illustrated in FIG. 1A. The event-related agency information 40 is formatted by the acquisition system 32 in a similar, or different, manner as that described above with respect to the event information 42 associated with a user 12.

The (318) system 10 then determines combinations of events, circumstances, and/or events. If the system 10 identifies a (320) correlation between event information 42 and event-related agency information 40, the system 10 determines if a (322) correlating document 46 is also available. A correlating document 46 is a document 46 that correlates to and/or includes as content within the document 46: an event, event record 62, event information 42, and/or event-related agency information 40 associated with a user 12. A correlating document 46 may, in effect, respond to event record(s) 62 or event information 42 and/or otherwise provide a benefit or value to a user 12. The correlating document 46 may also provide a user 12 with a remedy and/or avenue of relief based on event information 42 and/or agency information 40, including event-related agency information 40, associated with a user 12.

A user 12 may not be aware of the necessity or the availability of a particular correlating document 46 available to a user 12. Even if a user 12 was aware of the existence of a correlating document 46, a user 12 may not have access to the information necessary to determine whether or not a user 12 stands to benefit from a particular correlating document 46, or from the effect of a correlating document 46. Even if a user 12 fully appreciates the benefits of a correlating document 46, a user 12 may not be aware of where to locate, and/or how to properly complete a template of the correlating document 46 or, even more tasking, how to begin drafting the particular correlating document 46 from scratch. A user's 12 only alternative to performing the research, making the correlations, and properly drafting the documents 46 was to hire an agent, such as a lawyer or a law firm, to perform these tasks and generate a correlating document 46 for a user 12. The system 10 performs these tasks automatically by correlating personal information 30 associated with a user 12 with event information 42, and event-related agency information 40, to determine if a correlating document 46 is available for a user 12. The system 10 then automatically generates a correlating document 46 for a user 12. A user 12 may also utilize the system 10 to perform (336) follow-up search queries to event information databases 34 to provide the user 12 with monitoring and analysis of event information

A user 12 may (324) select a correlating document 46 for the system 10 to automatically generate, if the system 10, for example, fails to identify a correlating document 46 for a user 12, or for any other reason. The phrase “effect of the correlating document” refers to, for example, value, benefits, and/or opportunities available to a user 12, that include and/or as a result of a correlating document 46. For example, a document 46, such as a petition for expunction (as shown in FIGS. 12A-12E), offers little utility to a user 12 if the petition for expunction is not subsequently filed in the appropriate court or if a user 12 does not meet the statutory requirements for filing a petition for expunction. Thus, a correlating document's 46 benefits are in the document's 46 effect, when executed properly, not just the document's 46 existence. The system 10 may also be configured to provide electronic filing options 50 and/or provide a user 12 with instructions on how to file a particular document 46 manually in order to realize the effect of a document 46.

For example, the system 10 may locate event record(s) 62 and/or event information 42 associated with a user 12 (e.g., such as an arrest record 114 alleging that a user 12 committed a criminal offense). The system 10 may then locate another event record 62 or additional event information 42 associated with a user 12, or event information 42 associated with the same, or a different, event associated with a user 12 (e.g., such as a case disposition record 116 acquitting a user 12 of the criminal charge(s) documented in the first arrest record 114.)

The system 10 then correlates event-related agency information 40 with event information 42 found in the arrest record 114 and/or case disposition record 116 that suggests a beneficial correlating document 46 may be available to a user 12 (e.g., A statute that indicates an individual may direct the court to destroy or otherwise limit disclosure of an arrest record 114 if an individual is later acquitted of the charge). The system 10 then determines if a user 12 may benefit from a correlating document 46 (e.g., whether the event information 42 associated with a user 12 meets the requirements in a statute). If the system 10 determines that a correlation exists that may be beneficial to a user 12, the system 10 sends a notification 52 to a user 12 alerting a user 12 of the availability of the correlating document 46 and/or automatically generates a correlating document 46 for a user 12 (e.g., such as a Petition for expunction, Notice of Non-Disclosure, or other petition or document 46 that allows an individual to direct the court to destroy or limit disclosure of public records information).

A user 12, in this example, may not have been aware of the availability or utility of the correlating document 46. The correlating document 46 provides a user 12 with a mechanism to effect the removal of an arrest record 114 associated with a user 12. Individuals who are arrested and/or charged with a crime, and do not receive a final conviction, may mistakenly believe that the arrest record 114 is no longer visible to the public, because the arrest did not result in a final conviction.

Arrest records 114 and case disposition records 116 are often separate records that exist independently, possibly also residing on separate event information databases 34. Although a user 12 did not receive a final conviction, the arrest record 114 remains as a blemish on a user's background. The event records 62 associated with a user's 12 arrest may be misleading to an individual, such as an employer or future employer, who may discover an arrest record 114 associated with a user 12, but not a case disposition record 116 acquitting a user 12 of the criminal offense. The individual may assume that a user 12 actually committed an offense, and/or mischaracterize a user 12 as a criminal. By generating and filing a petition for expunction, a user 12 may seek to avoid detrimental consequences of having an arrest record 114 visible to the public, especially if a user 12 was acquitted or otherwise not convicted of a criminal offense alleged in an arrest record 114. Thus, the system 10 provides a user 12 with a process to manage a user's 12 reputation by limiting disclosure of event information 42 associated with a user 12.

Once the system 10 identifies a correlating document 46, the system 10 generates a correlating document 46 by populating fields on a document 46 template, referred to hereafter as a form 60, specifically designed to correlate with personal information 30, and event-related agency information 40, and event information 42 associated with a user 12. The form 60 or form(s) 60 are stored in a forms database(s) 58. A forms database 58, like the examples illustrated in FIG. 1A and FIG. 1C may consist of a near infinite variety of forms 60, or category of forms 60, that may be generated for variety of different users 12 and for a variety of purposes. Examples of such forms 60 illustrated in FIG. 1C include Trust templates 130, Wills Templates 132, Non-Disclosure Templates 136, Entity Formation and Agency law forms 138, and any other document forms 134. Once the system 10 populates the fields on a form 60, the system 10 completes generating a document 46 and makes the document 46 available for purchase by a user 12, for example, in a shopping cart 54 connected to the system 10. A user 12 may then download, print 68, and/or send the document 46 (334) as an attachment in an electronic message.

A user 12 may also execute or file a correlating document 46 using the system 10. For example, if the correlating documents 46 include a reply to a lawsuit filed against a user 12, a user 12 may digitally file correlating documents 46 with the appropriate court clerk directly from the system 10. The system 10 in FIG. 1A is configured to include, as an example, the e-file system 50 that digitally transmits, through secure connection, documents 46 directly to a court clerk or other agency. The system 10 may be configured to allow the user 12 to electronically transmit documents 46 to any agency or individual offering digital document 46 filing as an option for individuals.

The system 10 will also provide a user 12, or a user's 12 agent, with a means of which to receive notifications 52 from the system 10 when event information 42 associated with a user 12 becomes available and/or correlating documents 46 become available for a user 12. For example, the system 10 may send a notification 52 to a user 12, using the notification system 59, informing a user 12 that a newly enacted statute correlates with past event information 42 associated with a user 12 that makes available to a user 12, a correlating document 46, that may also benefit a user 12. The system 10 may also, for example, send a user 12 a notification 52 if the system 10 identifies a new arrest record 114 associated with a user 12, or if a past arrest record 114 now qualifies for the benefit of a correlating document 46 based on a correlation of the past arrest record 114 with event-related agency information 40. A notification 52 may alert a user 12 of event information 42 associated with a user 12 and correlating documents 46 the system 10 may automatically generate for a user 12.

The system 10 me be configured such that a user 12 may be better positioned to prevent or identify instances of misappropriation of a user's 12 personal information 30. For example, another individual associated with an event, may falsely claim the personal information 30 of a user 12. If an event record 62 is created with event information 42 associated with a user's 12 personal information 30, the system 10 may send a user 12 a notification 52, almost instantly, that may also include an event record 62 and/or event information 42, or other information, associated with a user 12. The system 10 may be configured to send search queries to event information databases 34 on a periodic, or continuous, basis to identify event information 42 associated with a user 12. The system 10 may then send search queries to agency information databases 36 in search of agency information 40, including event-related agency information 40, which may correlate to event information 42 associated with a user 12.

FIG. 4 is a flowchart 400 illustrating example operation of the system 10 in FIG. 1A. In the example of FIG. 4, the system 10 may automatically generate correlating documents, (e.g., a petition for expunction illustrated in FIGS. 12A-12E) for a user 12, in some cases, without the need for a user 12 to enter any personal information 30 after logging in to the system 10. In this example embodiment, a user 12 may login to a system 10, like the example system 10 in FIG. 1A, through a secured third-party service provider login 28, or using a traditional sap system login 24 described above.

Once a user 12 is logged in and authenticated by the system 10, the system 10 determines if event information 42 associated with a user 12 is available that correlates with event-related agency information 40 (e.g., in this embodiment, Chapter 55 of the Texas Criminal Code 124 information) and determines whether a correlating document 46 is available that may benefit a user 12 (e.g., a petition for expunction of public records associated with a user's 12 arrest record 114).

If the system 10 identifies correlating documents 46 for a user 12, the system 10 automatically generates correlating documents 46 for a user 12. A user 12 logs in to the system 10, and if correlating documents 46 that may be beneficial to a user 12 are available, a user 12 may select for the system 10 to automatically generate correlating documents 46. A user 12 may, for example, be presented with an option to purchase the complete, or partially complete, petition for expunction, and other correlating documents 46, and/or other additional services 64 (e.g., Order for Expunction, Letter to an Employer, Sending Notice to all Private Entities of an Order of Expunction, etc.) directly from the system's 10 shopping cart 54.

The system 10 may be accessed on a mobile device 18 or a computer 16 (or laptop), as well as other devices, such as an iPad or Kindle Fire. A user 12 logs in to the system 10 by viewing the interface 22 and typing on to a keyboard 14. A user 12 must enter login information (410), as described above in the description of FIG. 1A. A user 12 may be authenticated through the system 10 using a secured third-party service provider login 26, as described above, by having a user 12 enter a user's 12 username and password FIG. 2A, associated with an active account for a secured third-party service provider 26 (LinkedIn®, Facebook®, Westlaw®).

The system 10 authenticates a user 12 after a user 12 logs in to the system 10 and (412) the system 10 receives personal information 30 associated with a user 12 from the secured third-party service provider database(s) 28 (310). Once the system 10 authenticates a user 12, the system 10 sends a search query (414) to event information databases 34 for event information 42 and event records 62 associated with a user's 12 personal information 30. The event information databases 34 send back (416) event information 42 associated with a user 12 if event records 62 and/or event information 42 associated with a user's 12 personal information 30 are found on the respective database(s) (314).

If a user 12 accesses the system 10 through a secured third-party service provider login 26, the system 10 calls out by secure connection to the API of the secured third-party service provider's database(s) 28 using the account login information 26 provided by a user 12. The secured third-party service provider database 28 sends to the system 10 personal information 30 associated with a user 12. The system 10 receives the personal information 30 through the acquisition system 32.

The system 10 formats the personal information 30 in the acquisition system 32 and places formatted personal information 30 associated with a user 12 into the corresponding data fields 616 on the system database 56, based on the value or type of information collected (e.g., the source, subject, meaning, or content of the information, etc.). For example, an arrest data would be entered by the system 10 into the data field 616 that correlates with an arrest date.

Looking to FIG. 5, shown is an illustration of an example event record 62 sourced from event information databases 34 by the acquisition system 32. The event record 62 includes event information 42 associated with a user 12. The example event record 62 in FIG. 5 is for example purposes only and is not exclusive of the rich variety of event records 62 available to the system 10 as a result of sending search queries to event information databases 34. The type of event record 62, in this example, is a case disposition record 116 associated with an individual charged with a criminal offense. The example case disposition record 116 was sourced from the Fort Bend County, Texas District Clerk's event information databases 34. The case disposition record 116, and event information 42 contained in the case disposition record 116, may also be found on a variety of event information databases 34, including non-governmental entities that possess, collect, and/or aggregate event information 42. The case disposition record 116 in FIG. 5 includes a user's 12: full name 510, case number 512, sex 514, race 516, court name 518, address at the time of the charge 522, arrest date 524, the charged offense 528, and the final disposition of the charged offense 526, among other events and hearing information 520. Additional documents 46 of other events 520 may be scraped and downloaded by the acquisition system 32, in one of the variety of manners previously described. The system 10 may also be configured to utilize OCR 38 to quickly digitize large amounts of event information 42 in event records 62 that may be associated with a user 12.

The event record 62 may also include an individual record associated with a user 12, which is associated with an incident described in the event record 62. Generally, the incidents may refer to a single incident or multiple incidents associated with the duration of the overall event. A scenario, wherein multiple incidents are recorded for a single event is described in the following example: a person may be arrested for possession of a controlled substance, and additionally, during a subsequent stop by a police officer, may be arrested for speeding and driving while intoxicated. In accord with the context of the current disclosure, the overall event of the detainment and arrest of said person may include three incidents of possession of a controlled substance, speeding, and driving while intoxicated. Each incident may refer to a subset, or type, of event information 42 that may be related to separate portions of the agency information 40. In the case of the previous example, each of the three incidents may occur independently at separate times and be associated with different laws or ordinances stored in the agency information 40.

If the system 10 identifies event information 42 associated with a user 12, such as the event information 42 shown in FIG. 5, based on data matches with a user's 12 personal information 30, the acquisition system 32 formats the event information 42 and stores the event information 42 on the system database 56. The system database 56 organizes event information 42 associated with a user 12, and personal information 30 associated with a user 12, in specific data fields 616 on the system's 10 data tables 618. The system 10 may use these data fields 616 to identify correlating event-related agency information 40, and also to identify and generate correlating documents 46 for a user 12 by populating fields 1110 on the form 60 that correlate with the corresponding data fields 616 on the system's 10 data tables 618.

In the process of receiving event information 42, multiple event information databases 34 having at least a portion of the event information 42 may be accessed. It should be understood by those of skill in the art that in some circumstances, one event information database 34 may not contain sufficient event information 42 to determine eligibility for restricting access to certain records, sealing records, or expunction. As one example, event information 42 may be received from a first event information database 34 with respect to a single arrest event such that the event information 42 includes all of the event information 42 necessary to determine statutory eligibility for restricting access to certain related records, sealing the records, or expunction. The received event information 42 also preferably includes all of the necessary information to generate one or more appropriate documents and for filing the one or more documents with the appropriate authority. If event information 42 received from a second event information database 34 includes some but not all of the pertinent and relevant event information 42 received from the first database 34, system 10 is adapted and configured to disregard the incomplete and duplicate event information 42 so as to not mistakenly identify the incomplete event information 42 received from the second event information database 34 from being considered a separate event that could impact eligibility for restricting access to the records, sealing records, or expunction. Relatedly, in those circumstances when the event information 42 received from the second event information database 34 is as complete as the event information 42 received from the first event information database 34, system 10 is further adapted to disregard one of the sources and elects to use the event information 42 from the more reliable source. As an example of this, system 10 will preferably use event information 42 received from a governmental event information database 34 over the same event information 42 received from a third-party non-governmental event information database 34.

In another example, system 10 may receive event information 42 from a first event information database 34, and the event information 42 is incomplete. There is not enough event information 42 to determine eligibility, complete the document creation, and file the document with the appropriate authority. System 10 receives event information 42 from a second event information database 34 that includes both the missing event information 42 from the first event information database 34, as well as duplicate data also received from the first event information database 34. System 10 is further adapted to combine the event information 42 received from both the first and second event information databases 34 such that the combined event information 42 is sufficient to determine eligibility, complete the automatic document generation, and to file the document with the appropriate authority. System 10 is further adapted, in such instances, to disregard the duplicate event information 42 received from the second event information database 34. Although this example discusses receiving and coordinating event information from two event information databases 34, it should be understood that partial event information 42 may be received from more than two distinct event information databases 34, and the process of compiling the relevant event information 42 and disregarding duplicate data will proceed as herein described.

In another more specific example, system 10 receives from a first event information database 34 the following information: Arrest Offense=Assault; Date of Arrest=Jan. 2, 2003; Plea=No Contest; Disposition=Probation; and Disposition Date=Apr. 5, 2006. From a second event information database 34, system 10 receives the following data: Arrest Offense=Assault; Date of Arrest Jan. 2, 2003; Plea=No Contest; Disposition=Probation Complete; and Disposition Date=May 6, 2007. In order to qualify as eligible and to generate one or more appropriate documents, system 10 needs the most complete picture of the event. In this example, system 10 would utilize the later disposition date when determining eligibility and the like. In particular, system 10 uses both data points for eligibility determination, not only the data points of when the probationary term began, but also for when the probationary term ended. This is done for the purpose of calculating applicable waiting periods that must pass before being able to file a request for restricting access to the event information, sealing the records, or expunction.

In some instances, event information databases 34 may include event information 42 that is not properly presented. For example, if the event is an “Assault,” the term may be presented in an event information database 34 as “Asalt,” “Asssault,” or “Aslt.” In order to properly determine eligibility for restricting access, sealing records, or expunction, system 10 must recognize that all of the examples above relate to the same offense. To resolve such disparities in data presentation, system 10 preferably utilizes a table that normalizes theses offenses to assign these equivalents to a common code, or value, that has the proper statute and flags connected with it. System 10 can then recognize the appropriate offense, even when the event information 42 received contains a misspelling of the offense. This normalization process may be applied with any or all of the received event information 42.

The single event record 62, as illustrated in FIG. 5, although of course multiple events (records) may also be obtained, may be seen that in some implementations, various combinations of events, circumstances, and/or incidents may be identified and responded to with valuable and/or relevant documents 46. For example, a first event may be associated with a recent violation of a law by the user 12, while a second event may be associated with a violation of a deferred disposition agreement associated with another criminal offense. In this way, for example, event-related agency information 40 that is obtained and correlated with the event information 42 may be based on, or may include, information that takes into account such a combination. For example, such pluralities of offenses may carry the potential of different or stiffer penalties than each one alone. In another embodiment, a prosecutor may use the system 10 to automatically generate legal documents 46 associated with prosecuting a defendant being charged with a crime by sourcing the event information 42 associated with the defendant, including an information, indictment, and/or arrest records information contained in event information databases 34. In addition to automating the documents 46 for the prosecutor, the document 46 generation system 10 may be configured to consider event information 42 associated with the defendant (e.g., the defendant's criminal history) when generating documents 46, in order to properly charge the defendant with the more severe crime. For example, the document 46 generating system 10 may be configured to identify the past offenses in event information databases 34 and automate the form 60 to reflect the charge's increase in severity. A prosecutor who is prosecuting a defendant who resides in another jurisdiction may not be aware of the other charges and would thus not be able to consider this event information 42 associated with the defendant when drafting relevant legal documents 46 to be used for the purpose of prosecuting the defendant.

Service data 44 may be determined, based on the determined (event-related) agency information 40 and/or the determined event information 42. For example, as described above, the acquisition system 32 may access the service data 44, in order to supplement the event information 42 with personal information 30 associated with the user 12. In this way, particular attributes, evidence, or information associated with a user 12 (e.g., arrest records, case disposition records, social security number, arrest date, property interests) may ultimately be included in the document(s) 46.

At this point, in some implementations, a determined event record 62 may be correlated with corresponding event-related agency information 40. For example, the notification system 59 may select or determine an event and may then query a database in which the acquired agency information 40 is stored. For example, the event record 62 may include a filing for a marriage certificate by the user 12, where a query against agency information 40 downloaded from the agency information 40 and based on such an event may auto-populate a divorce document 46 using the event-related information that correlates with the agency information 40. A user 12 would be queried to complete the remaining portions of the document 46 without having to populate fields on the form 60 that contain event information 42 available in event information databases 34. The document 46 could be made readily available for a user 12 upon request or login to the system 10.

Then, a document 46 (e.g., For filing a divorce) may be generated. For example, the correlated event and event-related agency information 40 (and potentially the service data 44) may be included within a form 60 that provides for the filing of a divorce, and that is drafted specifically for the user 12. As referenced above, the information included in the personalized form 60 may be (re-) formatted, or otherwise cleaned or improved in appearance, either during the generation of the document, or earlier in the process. A personal notification 52 may be provided. For example, and as already described, the personalized notification 52 may be sent by mail or e-mail, or may be provided over a mobile device 18.

In other implementations, and as described with respect to some of the examples associated with FIG. 1A, a document 46 may be automatically generated after the system 10 identifies a user 12 and correlates event records 62 associated with a user 12 with the event-related agency information 40. In cases where a valuable document 46 is generated for the user 12, a letter, e-mail, or voicemail may be generated that includes basic or general information about the document(s) 46 and/or the benefits or purpose of the document(s) 46. In such cases, little or no information determined based on the job description (e.g., event information 42, event-related agency information 40, and/or service data 44) need not be included until a user 12 purchases or requests the document, although, in some implementations, a general reference to such document(s) 46, or to an availability of such document(s) 46, may be included in the notification 52.

By receiving the notification 52, a user 12 is informed of the existence and availability of personalized documents 46 and is provided with a technique for obtaining the personalized documents 46. For example, the notification 52 may include an address, e-mail address, website address, or phone number that a user 12 may use to download or access, a particular document 46 or obtain instructions on how to do so, (i.e., by providing the user 12 with access to the legal document 46 generating system 10).

Looking to FIGS. 6A1-6A3, each show an illustration of an example data table 618 on the system database 56, and data table 618 may be populated with a user's 12 event information 42. For purposes of this example, the system's 10 job data 48 is configured to determine whether a user 12 meets the statutory requirements required under Chapter 55 of the Texas Criminal Code 124 required for a user 12 to file a petition for expunction of public records. This data table 618, as illustrated in FIGS. 6A1-6A3, contains a user's 12 event information 42 that may be relevant to the system 10 when determining whether or not a user 12 meets the statutory requirements in the event-related agency information 40 in order to file this particular correlating document 46.

The data table 618 in FIGS. 6A1-6A3 is composed of rows and columns. The first column 610 identifies the category or particular type of event information 42 relevant to the system 10 when searching for correlations with the relevant event-related agency information 40. The second column 612 represents an example of the format of the possible values of the particular event information 42 associated with a user 12. Each row in the second column 612 is a data field 616 that may be populated by the system 10 with corresponding event information 42 associated with a user 12. For example, if the acquisition system 32 collects event information 42 associated with a user 12 that contains an arrest date, possibly in an arrest or case disposition record 116, the acquisition system 32 formats this particular event information 42 and places the event information 42, in this case, an arrest date, in the second column of this data table, on the row corresponding to arrest date. The third 614 and fourth columns are for reference purposes and identify the source and meaning of the event information 42 data fields 616, respectively. In this embodiment, the job data 48 and service data 44 are configured to express the event-related agency information 40 in Chapter 55 of the Texas Criminal Code 124 and determine if event information 42 associated with a user 12 meets the statutory requirements for a user 12 to file a petition for expunction. In this example, the system 10 data fields 616 and data tables 618 are specifically designed for the job data 48 and service data 44, whereof may be amended to accommodate other tasks, such as generating other documents.

In this embodiment, the system 10 in FIG. 1A searches for event information 42 associated with a user 12 that may suggest a user 12 was arrested and/or otherwise charged with committing a criminal offense. If relevant event information 42 associated with a user 12 is not found or insufficient to fully generate a correlating document 46, the system 10 will send a user 12 back to the system's 10 home screen where a user 12 may choose to view results of a user's 12 background check, based on the search results of event information 42 associated with a user 12, or to automatically generate correlating documents 46 by inputting information and/or answering system queries 712.

Looking to FIGS. 7A1-7A4 and FIG. 7B, each collectively form an example of an algorithm (420) that correlates a user's 12 event information 42 with relevant event-related agency information 40. The algorithm illustrated in FIGS. 7A1-7A4 and 7B is just one example of methods used to correlate event information 42 with event-related agency information 40, whereof would be available to the system 10. Algorithms, like the algorithm in FIGS. 7A1-7A4 and 7B, may be configured to accomplish a variety of different tasks and may be expressed through a variety of methods and scripts that are readable to the system 10.

Additionally, FIGS. 7A1-7A4 illustrate an example of the event information 42 component of the algorithm used in this application to correlate event information 42 with event-related agency information 40. FIGS. 7A1-7A4 are essentially a conversion table that instructs the system 10 to assign specific values720 to the variables (A-Z) 716, based on particular event information 42 that may be associated with a user 12 and available on the system database 56. The tables illustrated in FIGS. 7A1-7A4 have four columns, whereby the third and fourth column are continuations of the first and second columns, respectively. For purposes of clarity, the third and fourth column will each be referred to as the “first column” 710 and “second column” 714, respectively.

The first column 710 is a list of variables (A-Z) 716 and the second column 714 consists of job data 48 for the system 10 to run. The system 10 runs the job data 48 instructions in the second column 714 and assigns a numerical value (1-4) 720 to each variable, (A-Z) 716. The job data 48 in the second column 714 “Event information 42 Associated With User and Corresponding Value” consists of formulas, that utilize as components in the formulas, the specific event information 42 illustrated in the data table 618 in FIGS. 6A1-6A3. For example, if the data field 616 “Arrest Date” on the data table 618 in FIGS. 6A1-6A3 is not populated with a value (e.g., because the system 10 was not able to find an arrest date associated with a user 12), the system 10 assigns a numerical value 720 of 1 (e.g., A=1, if Arrest Date=no value) to Variable A 716. If, however, the “Arrest Date” data field 616 on the data table 618 in FIGS. 6A1-6A3 contains a value (e.g., event information 42 associated with a user 12 includes an arrest date) the system 10 assigns a numerical value 720 of 2 (e.g., A=2, if Arrest Date=value) to Variable A 710. In the same manner, the system 10 assigns a numerical value 720 to the remaining variables 716 in the first column 710 according to the job data 48 in the second column 714. FIG. 7B includes Queries 712 as Variables 716 in column one 710 that may be assigned a numerical value 720 according to the job data 48 in the second column 714 based on whether the user 12 responded with a “yes” or “no” to the query 712.

FIG. 7B illustrates an example of the event-related agency information 40 components of an algorithm, which correlates event information 42 with event-related agency information 40. In this particular embodiment, the event-related agency information 40 expresses event-related agency information 40 from Chapter 55 of the Texas Criminal Code 124. The algorithm may be reduced to a script or computer code readable by the system 10 and may be included in the system's 10 job data 48 and/or service data 44.

The system 10 begins the algorithm illustrated in FIG. 7B with the Variable A 716 in the first column of the table in FIG. 7B under Step 1. The letters (A-Z) in the first column 716 of FIG. 7B correspond to the variables A-Z 716 in FIGS. 7A1-7A4. The remaining columns in the table illustrated in FIG. 7B provide instructions for the system 10 to run, based on the numerical values (1-4) 720 the system 10 assigned to the variables (A-Z) 716 in FIGS. 7A1-7A4. The numerical value (1-4) 720 assigned to a particular variable 720 will determine the path the system 10 will take through the algorithm in FIG. 7B. If the instructions corresponding to a particular variable's 714 numerical value 720 instructs the system 10 to proceed 724, the system 10 proceeds to the next row in the table, thus proceeding through the remaining variables 714 in the algorithm alphabetically. For example, if variable A 716 from FIG. 7A1 is assigned a numerical value 720 of 2 (e.g., meaning that arrest date=value), the system 10 follows the instructions in the box corresponding to A=2 724, and instructs the system 10 to proceed to the next row of the algorithm, variable B. If, however, no arrest date information is available in the Arrest Date data field 714 in FIG. 7A1, then A=1, and the algorithm instructs the system 10 to communicate “Message 1” as one of the possible messages 718 (as shown in FIGS. 7B, 7C1, 7C2) to a user 12, possibly using a notification 52 from the notification system 59. The Message from the system 10 to a user 12 may also be communicated in the form 60 of a pop-up, or similar text object, that a user 12 views on the interface 22 of a user's 12 computer 16 or mobile device 18.

FIGS. 7C1-7C2 illustrate an example table consisting of messages 714 and queries 712 that the system 10 may communicate to or request from a user 12, based on the instructions of the algorithm in FIGS. 7A1-7A4 and 7B. The notification system 59 triggers a query 712 or message 714 to a user 12 that is viewed on the interface 22 of a user's 12 computer 16 or mobile device 18. The system 10 may also be configured to query 712 a user 12 as a method of verifying event information 42 associated with a user 12. For example, queries 712 could automatically be triggered if event information 42 associated with a user 12 correlates with event-related agency information 40, but the system 10 wants to verify that the event information 42 associated with a user 12 is actually a user 12, and not another individual.

The system 10 may also query 712 a user 12 to offer additional services 64 or to collect additional information from a user 12. The system 10 may continue to generate documents 46 in the event a user 12 ignores queries 712 from the system 10. However, the queries may provide a user 12 with insight on risks that a user 12 may be exposed to during the process of generating and/or filing a petition for expunction and/or based on particular event information 42 associated with a user 12. If the algorithm in FIG. 7B instructs the system 10 to “Generate Form” 722, the system 10 begins generating a correlating document 46 (e.g., the petition for expunction, as shown in FIGS. 12A-12E, of public records) for a user 12. The Generate Form 722 instructions indicate that a correlation exists between event information 42 associated with a user 12, event-related agency information 40, and a correlating document 46, the petition for expunction of public records (422). In other words, event information 42 associated with a user 12 meets the statutory requirements for a user 12 to file a petition for expunction of event records 62, according to Chapter 55 of the Texas Criminal Code 124.

A formatting system 74 may further format event information 42 and personal information 30 associated with a user 12 to correlate with fields on a particular template form 60 that is used by the system 10 to generate a document 46. The formatting system 74 may also receive event information 42 and personal information 30 in many forms 60, and then store the event information 42 and personal information 30 associated with a user 12 on data tables 618 designed to populate a particular form 60. A formatting system 74 may be employed to clean or otherwise reformat data in the job data 48. For example, the formatting system 74 may appropriately title case words in the job data 48 (i.e., may re-format words in all-capital letters to use appropriately capitalized/un-capitalized letters) (332). As another example, the formatting system 74 may check address information 830 associated with a user 12 or any other address, such as the address of a governmental agency 122, that is listed in the document 46, e.g., to include or correct zip code information, or otherwise make ready at least some of the job data 48 for delivery to a user 12. The system 10 will assign values to the event information 42 based on the source and content of particular event information 42 associated with a user 12. The formatting system 74 then sends any formatted event information 42 and personal information 30 into data fields 616 that correspond to the numbered fields 1110 on the correlating documents 46.

After running the algorithm, shown for illustrative purposes in FIGS. 7A1-7A4 and 7B, the system 10 may display (424) to a user 12 any event information 42, arrest and/or criminal offense and case disposition records 116, associated with a user 12. If event information 42 associated with a user 12 meets the statutory requirements for filing a petition for expunction of public records, a separate category of event information is listed for the user 12 to view (426) to shows criminal offense information that meets the statutory requirements for the user 12 to file a petition for expunction. A user 12 may click on a link to (428) complete on a corresponding link to begin generating the necessary documents 46. The system 10 selects (430) the appropriate legal forms 60 from the legal forms database 58. (In this example, a form 60 is used to generate a petition for expunction as shown in FIGS. 12A-12E). The system 10 may generate additional documents 46 for a user 12 that correlate to the correlating document 46, the petition for expunction. Additional documents 46 include, for example, an order of expunction, civil case filing form, letters to an employer, notice letters to private entities possessing event information 42, and other correlating documents 46 to the petition for expunction generated for a user 12. The system 10 may generate a Notice of Nondisclosure for a user 12 who meets the statutory requirements for this document 46, but, perhaps, may not meet the statutory requirements for filing a petition for expunction. Although both documents 46 effectively limit disclosure of event information 42 associated with a user 12, a user 12 may have a preference for a particular correlating document 46 over another correlating document 46. If a user 12 meets the statutory requirements for more than one correlating document 46, the system 10 may select a particular correlating document 46 or query a user 12 to select a correlating document 46 from a list of possible options identified by the system 10.

Once the system 10 identifies and selects the relevant correlating documents 46, based on the job data 48, the system 10 generates correlating documents 46 by populating (432) numbered fields 1110 on a template form 60, referred to throughout this description as a form 46. A form 60 contains numbered fields 1110 that correlate with personal information 30, event information 42, and/or event-related agency information 40 data fields 616 associated with a user 12. These numbered fields 1110 contain information that must be included in the correlating documents 46. The form 60 or form(s) 60 are stored in a forms database(s) 58 on the system 10.

Looking to FIG. 8A, shown for illustrative purposes is an example of event-related agency information 40 processed by the system 10. A petition for expunction generated by the system 10 includes a list of all law enforcement agencies 814 in a petition for expunction generated for a user 12. FIG. 8A is an excerpt of Chapter 55 of the Texas Criminal Code 124. This chapter correlates to event information 42 associated with a user 12 who may be interested in filing a petition for expunction of event information 42 associated with the user 12. The event-related agency information 40 in FIG. 8A also correlates to a document 46, a petition for expunction. The system 10 correlates the event information 42 associated with a user 12 with event-related agency information 40, like in FIG. 8A, and may determine if a user 12 meets statutory requirements for filing a petition for expunction. If the system 10 determines that a correlation exists that indicates a user 12 meets the statutory requirements in the event-related agency information 40, the system 10 searches a forms database 58 for a petition for expunction. The system 10 then correlates a petition for expunction with event-related agency information 40, and event information 42 associated with a user 12 that correlates with numbered fields 1110 on a form 60 used by the system 10 to generate a petition for expunction as shown in FIGS. 12A-12E.

FIG. 8A contains event-related agency information 40 the system 10 may use to determine which personal information 30 and event information 42 associated with a user 12 must be included in a petition for expunction, as illustrated in FIGS. 12A-12E. The event-related agency information 40 in FIG. 8A also correlates with agency information that must be included in a petition for expunction according to event-related agency information 40 (see 814 for agency information that is also event-related agency information 40 contained in event-related agency information 40). A petition for expunction generated by the system 10 complies with event-related agency information 40 by including in a petition for expunction all required information that must be included in a petition for expunction, according to the event-related agency information 40 in the statute used as an example, Chapter 55 of the Texas Criminal Code 124.

The event information 42 to be included in a petition for expunction is event information 42 in event records 62 collected by the system 10 from event information databases 34 that must be included in a petition for expunction, according to the event-related agency information 40. Event information 42 that must be included in a petition for expunction includes a user's 12 full name 510, sex 514, race 516, address at the time of arrest 522, the offense charged 528 against a user 12, the date of arrest 524, case number 512, and the court of offense 518. Agency information 40, that may also be event-related agency information 40, and that also must be included in a document 46, according to event-related agency information 40 is a list of law enforcement agencies 814 that are suspected of possessing event information 42 associated with a user 12 with respect to the arrest or criminal offense 528 the user 12 seeks to expunge.

Looking to FIGS. 8B1-8B2, shown for illustrative purposes is an example of event-related agency information 40 b,40 c processed by the system 10. A user 12 who is arrested or charged with a crime proceeds through the criminal justice process 816. During this time, a user 12 will proceed and communicate with a variety of agencies based on a user's 10 charges and final case disposition. Various governmental entities may transact with a user 12 in the criminal justice process 816 and generate event records 62 associated with a user 12. Governmental entities also transmit event records 62 and event information 42 associated with a user 12 to other private and governmental entities. FIGS. 8B1-8B2 are an example of event-related agency information 40 b,40 c that the system 10 considers in an algorithm that identifies which governmental entities possess event information 42 associated with a user 12. By correlating event information 42 associated with a user 12, with event-related agency information 40 b,40 c in FIGS. 8B1-8B2, the system 10 may identify a user's 12 transactions with governmental entities during the criminal justice process 816. For purposes of generating a petition for expunction, the system 10 generates a list of law enforcement agencies 814 suspected of possessing event information 42 associated with a user's 12 arrest and/or criminal offense. The system 10 first identifies the names of governmental entities that are contained within event records 62 and event information 42 collected by the system 10. The system may utilize OCR 38 or any of the other techniques for collecting and analyzing data described above. The system 10 then determines which agencies may also possess event records based on the user's 12 path through the criminal justice process 816. The system 10 may include a governmental entity on the list of law enforcement agencies 814 contained in a petition for expunction if a governmental entity is 1) a source of event information 42, 2) named, or is a party to, event information 42 associated with a user 12, and/or 3) a particular governmental entity if the system 10 determines a governmental entity transacted with a user 12 as a result of the criminal justice process 816.

Looking to FIGS. 8C1-8C2, shown for illustrative purposes is an example of event-related agency information 40 d,40 e collected by the system 10. FIGS. 8C1-8C2 are an example of a governmental entity's data migration policy 126. The example county clerk reporting requirements 126 in FIG. 8C2 illustrate an example of agency information 40 that is also event-related agency information 40 d,40 e and describes the data migration policy 126 of a particular governmental entity, in this example, a county clerk. FIGS. 8C1-8C2 list the event record 62 or event information 42 that is transmitted to another governmental entity in one column 820, the recipient governmental entity and their contact information 122 in another column 822, and when the event record 62 or event information 42 is sent 824. By correlating event-related agency information 40 in FIGS. 8C1-8C2 with event information 42 associated with a user 12, the system 10 may determine whether or not a particular governmental entity possessing event information 42 associated with a user 12 and/or also generated or transmitted event information 42 to another governmental entity, based on the particular governmental entity's data migration policy 126 for a particular event record 62. The system 10 queries agency information databases 36 for the data migration policy 126 information associated with a governmental entity, if the governmental entity is 1) a source of event information 42, 2) named, or is a party to, event information 42 associated with a user 12, or 3) if an entity transacted with a user 12 as a result of the criminal justice process 816. The data migration policies 126 of these governmental entities will identify additional governmental entities that are suspected of possessing event information 42 associated with a user 12 by determining whether a particular governmental entity received event information 42 from another governmental entity, based on the data migration policy 126 of a governmental entity known or suspected by the system 10 of possessing event information 42 (e.g., For example, when the system 10 collected event information 42 from that governmental entity or because the system determined that a governmental entity transacted with a user 12 during the criminal justice process 816.).

Looking to FIG. 8D and FIG. 8E, shown for illustrative purposes are examples of data tables 618 listing contact information 122 of specific governmental entities. The first column in FIG. 8D is a list of court names 518, and the second column identifies the type of court 826. The third column identifies the county 828 associated with a particular court name 518. The address and contact information 122 for the court is also available in this data table 618 in the remaining columns of the data table 618. The system 10 may use this agency information 40 to, for example, populate a document 46, transmit a document 46 to a governmental entity, or provide a user 12 with a court's contact information 122. In this embodiment, the system 10 correlates the names from the list of law enforcement agencies 814 with the contact information 122 for the particular law enforcement agencies on contained in the list of law enforcement agencies 814. The name and contact information 122 of the list of law enforcement agencies 814 are aggregated and placed on a data table 618 on the system database 56. Once formatted properly, the data fields 616 containing the list of law enforcement agencies 814 are matched with the correlating numbered fields 1110 on the template form 60 used by the system 10 to generate a petition for expunction for a user 12. FIG. 8E illustrates an example data table of law enforcement agencies for each county 832. The first column identifies the name of the county 832 and the second column lists law enforcement agencies 834 located in the particular county name 832 in column one.

The system 10 automatically generates a list of law enforcement agencies 814 suspected of possessing event information 42 associated with a user's 12 arrest or criminal offense. The system 10 may run a script expressing an algorithm that calculates the data migration of event records 62 associated with an event, or series of events, associated with a user 12 based on agency information 40 associated with a governmental entity's data migration policy 126.

Looking to FIGS. 9A-9B, shown for illustrative purposes is a table with job data 48 a directing the system 10 to generate a list of law enforcement agencies 814. The job data 48 a considers the governmental entity that created the event record 62 or event information 42, the data migration policy 126 of that governmental entity with respect to a particular type of event record 62, and the data migration policy 126 of any governmental entity recipients of event information 42 from the particular governmental entity that generated the event record 62 and/or event information 42. The job data 48 a also considers state and federal criminal reporting requirements, including the (UCRA) Uniform Crime Reporting Act to determine if additional law enforcement agencies should be included in the list of law enforcement agencies 814. The first column 910 contains law enforcement agencies that may transact with a user 12 during the criminal justice process 816. The data migration variables (A-M) 912 listed in the second column of FIGS. 9A-9B correlate to the law enforcement agencies in column one 910 and the event-related agency information 40 associated with a transaction in the Criminal Justice Process 816. The remaining four columns contain job data 48 specific to the type of criminal offense: Felony 914, Class A Misdemeanor 916, Class B Misdemeanor 918, and Class C Misdemeanor 920, respectively.

The system 10 identifies any governmental entities that are identified in event records 62 and event information 42 collected by the system 10, regardless of whether that particular governmental entity created the event records 62 and event information 42, in order for the system 10 to include these governmental entities in the list of law enforcement agencies 814. Once the list of law enforcement agencies 814 is generated, the system 10 populates the mailing address and/or e-mail (depending on the notice requirements when filing the petition for expunction.) of the respective governmental entity using agency information 40 sourced from agency information databases 36. The system 10 then populates this information into the appropriate field or position of the petition for expunction as illustrated in FIGS. 12A-12E.

Looking to FIG. 10A, shown for illustrative purposes is an example of a data table 618 with data fields 616 that contain personal information 30 and event information 42, represented with bracket 42′, associated with a user 12 used by the system 10 to populate the petition for expunction. The data table 618 illustrated in FIG. 10A is an example of a data table 618 that contains data fields 616 correlating to numbered fields 1110 on a particular form 60 and is not exclusive of the possibilities of data tables 618 or data fields 616 that may be utilized in the system 10. The data table 618 in FIG. 10A includes twenty-three (23) data fields 616. The numbered data fields 616 on this data table 618 correlate to numbered fields 1110 on a form 60 used by the system 10 to generate documents 46 for a user 12. The first column 1010 lists the numbered field 1110 on a form 60 that a particular data field 616 correlates with. The second column 1012 is for information purposes and may be included in the system's 10 job data 48 to direct the system 10 as to which event information 42 and/or personal information 30 to search for and collect in order to populate a particular data field 616. The third column 1014 illustrates data fields 616 correlating to a particular numbered field 1110 on a form. The formatting system 74 formats event information 42 and personal information 30 collected by the acquisition system 32 that correlates to a numbered field 1110 on form 60. Once formatted, the formatting system 74 may place the formatted information into data fields 616 until the system 10 needs them to populate a correlating numbered field 1110 on a form 60. FIG. 10B is a data table 618 b that the system 10 uses to populate numbered fields 1110 on the form 60 that correlate with the list of law enforcement agencies 814 contained within a petition for expunction.

Looking to FIGS. 11A-11E, shown for illustrative purposes is an example of a Form 60 that will be populated by the system 10 to create a petition for expunction for a user 12. The black squares containing white numbers illustrate examples of numbered fields 1110 on a form 60. The system 10 correlates data fields 616 on the system database 56 with (e.g., in this example, the data fields 616 on the data tables 618,618 b illustrated in FIG. 10A and FIG. lOB) with correlating numbered fields 1110 on a form 60 to generate a correlating document 46 for a user 12. The form 60 that the system 10 populates is based on the correlations of agency information 40 and event information 42 associated with a user 12. For example, this particular form 60 illustrated in FIGS. 11A-11E is designed to generate a petition for expunction of public records for a user 12 who meets the statutory requirements under Chapter 55 of the Texas Criminal Code 124 to have a criminal offense record and/or arrest record 114 expunged, because the criminal offense charged against a user 12 did not result in a final conviction. The system 10 may utilize a different form 60, for example, if a user 12 qualifies under a different statute or for any other reason.

Looking to FIGS. 12A-12E, shown for illustrative purposes is an example of correlating documents 46 a generated by the system 10 for a user 12 by populating the numbered fields 1110 on the form 60 in FIGS. 11A-11E with the information from the data fields 616 in FIG. 10A. In this example, the system 10 generated a petition for expunction, as shown in FIGS. 12A-12E, for a user 12 after determining that the event information 42 associated with a user 12 met the statutory requirements contained within the event-related agency information 40. A petition for expunction is personalized for a particular user 12. A petition for expunction, as shown in FIGS. 12A-12E, includes event-related agency information 40, personal information 30, agency information 40, and event information 42 associated with a user 12. Although FIGS. 12A-12E focus on a petition for expunction, and much of this description likewise focuses on the generation of documents related to expunction, it should be understood that some jurisdictions do not provide a statutory basis for expunging records. Rather, some jurisdictions provide a way to restrict access to the underlying event information 42 in compliance with relevant law. In some such jurisdictions, there may be a defined process, often by statute, to provide for the sealing of certain records when the statutory requirements for doing so are met and any request for sealing such records has been duly made. Any such documents necessary to restrict access to certain event information 42 and/or to seal certain records relating to the event information 42 may be generated by system 10 in accordance with the methods herein described.

Private entities may compile and disseminate, possibly for compensation, event information 42 that includes criminal and/or arrest records 114, and case disposition records 116 associated with a user 12. These private entities may be included in the list of law enforcement agencies 814 in the petition for expunction. If the petition for expunction is filed, the private entity will receive notice of the hearing associated with a user's 12 petition for expunction. In Texas, however, private entities may not challenge a petition for expunction. The system 10 may exclude these private entities off the list of entities on the petition for expunction, because the private entities may not challenge the petition for expunction, and the private entities must comply with an order of expunction signed by the judge. An order of expunction is a document 46 that a judge signs if the court grants a user's 12 petition for expunction. In Texas, an individual who is in possession of event information 42 or event records 62 that are subject to an order of expunction may be charged with a Class B Misdemeanor. The system 10 may query event information databases 34 associated with private entities (e.g., background check companies, mug shot websites, etc.) to determine if a private entity possesses event information 42 associated with a user 12 and is subject to an order of expunction. The system 10 may then automatically generate a demand letter to be sent to the private entity directing the private entity to destroy or return to a user 12 the event information 42 subject to the order of expunction.

The system 10 searches the Internet, and possibly other networks 20, for private entities and other websites that the system 10 suspects of possessing event information 42 related to a user's 12 petition for expunction. Once a user 12 files a petition for expunction with a Court Clerk (Either through e-file 50 or in-person), a user's 12 trial date(s) and the case filing history becomes event information 42 contained in an event record 62 stored in event information databases 34, among other places.

If the system 10 cannot populate all numbered fields 1110 with the information sourced from the various sources, the system 10 queries (436) the user 12 in order to populate the remaining numbered fields 1110 on the form 60 required to generate the documents 46. Once the numbered fields 1110 on a form 60 are populated, the correlating documents 46 are generated, and the correlating documents 46 may be purchased by a user 12, for example, in a shopping cart 54 connected to the system 10. The system 10 may then allow a user 12 to download 66, print 68, (452) or send the correlating documents 46 as an attachment in an electronic message.

Once a user 12 completes a transaction (438) and places the documents 46 in the shopping cart 54 on the system 10, a user 12 may also (440) download 66, print 68, save, edit, or e-mail documents 46. A user 12 may then (442) e-file 50 the petition for expunction with an appropriate Court Clerk, directly from the system 10. The system 10 will provide a user 12 with directions 70 to a (446) Court Clerk and provide a user 12 with a completed filing request form 60 containing the cost of filing a document 46, according to event-related agency information 40.

The system 10 calls out search queries to event information databases 34 for event records 62 associated with a user 12 or a document 46 that was filed by a user 12. For example, the system 10 may collect (448) event records 62 associated with case filings in the Jurisdiction where a user 12 filed a document 46. The system 10 may send notifications 52 to a user 12 if there are any new updates on the status of a document 46 filing, including confirmation (444) that a court clerk received the documents 46 by e-file 50, and provide other event information 42 to a user 12. The system 10 uses this event information 42 in order to send personalized notifications 52 to a user 12 associated with upcoming trial date(s) (450) or any other updates or changes to the status (456) of a user's 12 filing by correlating event information 42 associated with a user 12 in the calendar to the event-related agency information 40 associated with the rules of civil and criminal procedure for a particular jurisdiction. A user 12 may also access the system 10 to check the (454) status of user's 12 petition for expunction filing.

The system 10 may be configured to automatically generate a variety of beneficial documents 46 for a user 12. These documents 46 may include documents 46 associated with creating wills 132, trusts 130, divorce documents, pre-marital agreements, corporate or agency law 138, or any other type of document 46 template 134 that a user 12 may desire. The system 10 may also be configured to allow a user 12 to upload their own forms 60 for the system 10 to automatically generate into documents 46. A user 12 may, for example, identify numbered fields 1110 on the form 60 for the system 10 to populate with event information 42 and personal information 30 associated with a user 12. A user 12 may configure the job data 48 to correlate specific information to specific fields on the forms 60. The system 10 may then populate the fields with information associated with a user 12 on the system database 56. A user 12 may create or edit data may benefit from the automated generation of these documents 46. For example, a user 12 may have specialized knowledge related to a particular class of the agency information 40, such as a criminal defense attorney with knowledge of a criminal code, and the system 10 could be configured to include only the agency information 40 related to the agency information 40 or event-related agency information 40 that is of interest and/or associated with a user 12 and/or a user's 12 client.

A user 12 may wish to use the system 10 to minimize the time required to generate a document 46, while maximizing the accuracy of the document 46. By using the automatic document 46 generation system 10, a user 12 may generate documents 46 that only require user 12 input in the fields 1110 on a form 60 that are not automatically populated with personal information 30 or event information 42 associated with a user 12. A user 12 may review the document 46 and make changes to any fields 1110 on the form 60 that may be incorrect or require editing based on possible errors or inaccuracies found in the event information 42 or personal information 30 associated with a user 12 and collected the system 10 using the above-described methods of data collection.

Of course, techniques described herein are merely examples, and many other modifications and implementations are possible. For example, a user 12 may include, or refer to, more than one user 12, or to an entity, e.g., a corporate entity. As another example, looking back to FIG. 1A may include an artificial intelligence engine as part of the rule engine previously mentioned, and configured to determine the inferred event from the event information 42.

Thus, while certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes, and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the embodiments of the invention.

Looking to FIG. 13, shown is a flowchart 1300that illustrates an alternative embodiment of the methods described while referencing system 10 as it is shown in FIG. 1A. In the example of FIG. 13, as described with respect to FIG. 1A, (1310) a user is first authenticated from a secured third-party login 26, (1312) a job description is determined, (1314) agency information 40 is determined, (1316) event information 42 is determined, (1318) then an inferred event may be determined or obtained by the acquisition system 32 from the event information 42, based on the job description. For example, the job description may request for all or some of that information from event information databases 34, so that the acquisition system 32 may query the event information 42 based on such information to obtain the event information 42 as a subset of the event information 42 (e.g., by querying the event information 42 for all arrests or criminal charges associated with the user 12, as specified in the user's 12 personal information 30 received from the secured third-party service provider databases 28. In the example of FIG. 1A, as described with respect to FIG. 13, a job description is determined, agency information 40 is determined, and/or event information 42 is determined. Then, an inferred event is determined, based at least on the event information 42. The inferred event is (1320) correlated with event-related agency information 40, (1322) then the inferred event and or event-related agency information 40 is correlated with a document 46. The system 10 then (1324) selects a form and generates a correlating document 46 and/or notifications 52 by correlating the information with the correlating fields 1110 on a form 60 in order to populate the form 60 and generate a document 46.

For example, as referenced above, an event may include a judgment against a user 12 by a Court, or by any other governmental agency. If such a judgment is very large, or if the event information 42 includes a default on the judgment by the user 12, then an inferred event, e.g., a current or future bankruptcy of the user 12, may be determined and the correlating documents 46 may be generated using the public record information to begin the automation of the documents 46.

For example, the acquisition system 32 and/or the notification system 59 may be configured to implement a rule engine that executes inference rules based on the event information 42. For example, a rule may be implemented that states that when a damages amount may be too excessive to file in a particular Court based on the event-related agency information 40, (e.g., $100,000, or $5,000,000 limits on damages that may be sought) may trigger an inference of the inferred event (e.g., the Court or venue is not proper). Many other examples of such rules and inferences may be implemented. For example, the lawyer or law firm may be interested in generating documents 46 for creating a trust account. The acquisition system 32 can source public record information associated with users 12 named in a legal document 46 being generated to determine if a user 12 is associated with event information 42 that may disqualify a user 12 from being a trustee (e.g., a user 12 is a minor or is convicted of a felony). The lawyer or law firm can configure the notification system 59 to send a notification 52 to a user 12 if a user 12 types in a value in a numbered field 1110 on a form 60 that correlates with agency information 40.

Accordingly, the inferred event may be correlated with event-related agency information 40. For example, in the examples just given, the inferred event of bankruptcy may be correlated with event-related agency information 40 associated with relevant bankruptcy laws. Or the inferred event of a filed lawsuit or right to file expunction may be correlated with event-related agency information 40 associated with agency information 40 required to file a document.

In another example of the operations of FIG. 1A, it may be the case that the event includes a filing for a business license by the user 12. Then, the inferred event may include a need for a trademark filing, or other business-related needs. Accordingly, the (inferred) event-related agency information 40 may include event-related agency information 40 regarding trademark filings or procedures, such as might be obtained from the U.S. Patent Office, and/or agency information 40 related to the business license. This information may then be used to infer the legal action to be taken and/or to generate the legal documents 46 at the request of, or as a suggestion to, the user 12. A notification 52 may be generated and sent to the user 12 and a correlating document 46 may be generated by the system 10 for a user 12.

A formatting system 74 may be used to clean or otherwise reformat data in the job data 48. For example, the formatting system 74 may appropriately title case words in the job data 48 (i.e., may re-format words in all-capital letters to use appropriately capitalized/un-capitalized letters). As another example, the formatting system 74 may check address information associated with a user 12 or any other address, such as the address of a governmental agency 830, that is listed in the document 46, e.g., to include or correct zip code information, or otherwise make ready at least some of the job data 48 for delivery to a user 12. The public records include “event records” 62, which may refer to any data or information that relates to an individual or group of individuals, such as, for example, a user 12. For instance, and to reiterate the examples above, FIG. 1B illustrates that the event information 42 may include governmental information, tax information, property ownership information 112, legal information (e.g., court-related or law enforcement information), corporate and other company filings 110, arrest or criminal charge records 114, and case disposition records 116, or credit reporting information 146 (shown in FIG. 1C), etc. More specifically, the public information referred to as “agency information” includes information which is generally not associated with, but is applicable to, a user 12 and/or to the document 46 generated by the system 10 for a user 12, and also may include event information 42, which includes event information 42 that is related to a unique event in which a user 12 was a participant, such as an arrest or criminal offense.

For example, agency information 40 may include information related to laws, statutes, or rules that are codified by a local, state, or national legislature or administrative agency, as well as the internal agency policies and contact information 122, including data migration policies 126, of these governmental or political agencies. Such information is therefore, as just mentioned, generally not specific to a user 12, but may be applicable or useful to a user 12 in a specific circumstance or for identifying and generating a particular correlating document 46. In contrast, the event information 42 includes an event record 62, which includes event information 42 related specifically to a user 12 or mentioning a user 12, (e.g., event information 42 that describes an event in which a user 12 was arrested for allegedly committing a criminal offense).

In another example, the event record 62 may include event information 42 regarding a circumstance in which a user 12 was arrested or detained, or otherwise involved in a violation or alleged violation of the law. As another example, the event record 62 may include event information 42 regarding a circumstance in which a user 12 was arrested for a separate criminal offense, tried for the charge stemming from the arrest, and subsequently acquitted by the Court.

The event record 62 may include information regarding a filing or request provided by a user 12 to an agency or authority associated with the agency information 40. For example, a user 12 may file a request for a business license (e.g., to start a company in a municipality) or file a marriage license 118 or may file a lien or mortgage on a dwelling or other structure. A user 12 may file a complaint with a governmental agency, (e.g., against the same or a different agency, or against a separate business). A user 12 also may file a lawsuit or may have a lawsuit filed against him or her, or may have a judgment issued for or against him or her (e.g., by a court, or by another governmental agency, such as the Department of Public Safety (DPS)).

Generally, then, the event(s) of the event information 42 may include any event in which a user 12 may have been involved, or in which a user 12 may currently be involved or may be involved in the future. Further, as described in more detail below, the event information 42 may include at least some event records 62 to which at least some agency information 40 may apply. That is, for example, the agency information 40 may include a large number of laws, codes, statutes, or rules, while the event information 42 may include a large number of event records 62. Moreover, although illustrated in FIG. 1B (for the sake of clarity and convenience) as being included within the public records information, it should be understood that the agency information 40 and the event information 42 may be stored in separate locations (e.g., separate databases and/or separate sites on the network 20, or on different networks 20), in separate formats, and perhaps requiring different interface techniques.

Further, the agency information 40 may itself include a large number of the same or different types of agency information 40, only some of which may be related to a given (one or more of the) event records 62, where the included agency information 40, again, may be stored using different locations, formats, and/or interfaces. Similarly, but conversely, the event information 42 may include a large number of event records 62 that may be stored using different locations, formats, and/or interfaces, where only some of the event records 62 may relate to any or all of the agency information 40.

Looking briefly to FIG. 5, an example of an event record 62 is shown for illustrative purposes, whereof may include one or more incidents. For example, the event record 62 may include an individual record associated with a user 12, which is associated with an incident described in the event record 62. Generally, the incidents may refer to a single incident or multiple incidents associated with the duration of the overall event. A scenario, wherein multiple incidents are recorded for a single event is described in the following example: a person may be arrested for possession of a controlled substance, and additionally, during a subsequent stop by a police officer, may be arrested for speeding and driving while intoxicated. In accord with the context of the current disclosure, the overall event of the detainment and arrest of said person may include three incidents of possession of a controlled substance, speeding, and driving while intoxicated. Each incident may refer to a subset, or type, of event information 42 that may be related to separate portions of the agency information 40. In the case of the previous example, each of the three incidents may occur independently at separate times and be associated with different laws or ordinances stored in the agency information 40.

In an alternative embodiment, the system 10 may perform a variety of tasks or jobs. An example of one of these jobs or tasks, demonstrated in this description, is identifying a user 12 upon login, and automatically generating a petition for expunction, as shown in FIGS. 12A-12E, for a user 12. The system 10 searches for arrest and or criminal offense information associated with a user 12, determines whether a correlation exists with the event-related agency information 40 and a correlating document 46 that may benefit a user 12, and automatically generates the correlating documents 46 for a user 12 using a variety of information from a variety of sources explained in more detail below. Alternative Embodiments

Alternative embodiments, whereof are still being contemplated by the inventor, will undoubtedly incorporate new or adjusted algorithms in addition to the algorithms represented in FIGS. 7A1-7C2 and FIGS. 9A-9B. The additional algorithms, when combined with more correlating information and forms 60 (See FIG. 1C for examples of different forms databases 58), will allow the system 10 to generate correlating documents 46 for a variety of purposes that comply with requirements in agency information 40. The system 10 may be configured for increased functionality and document automation for a user 12 by correlating events, services, and information associated with a user 12. The system 10 may be configured to search and collect information associated with a user 12 from secured third-party service provider databases 28, correlating with more agency information 40 converted into algorithms to be processed by the system 10, in order to limit the need for user 12 input while providing verification of user 12 input based on a user's 12 responses to queries used to populate a particular field on a form. The system may query the relevant information databases associated with a field 1110 to determine if a user's 12 entry may contain an error. For example, a user 12 may enter an incorrect name in a field 1110 on a form 60, and the system 10 may query information databases associated with a user 12 to determine if the entry is incorrect.

An alternative embodiment may review user 12 populated sections of a legal document 46 to see if a user 12 who may be the subject of a contract or legal instrument fails to meet agency information 40 requirements associated with that particular field 1110 and event information 42 disqualifying the subject individual. That is, if a user 12 is forming a contract with someone who is legally incapacitated, the system 10 can alert a user 12 that event information associated with the subject individual renders the subject individual incapacitated to enter a contract. The system 10 may reach this determination by correlating the user's 12 entry for a particular field 1110 on a form 60 with event information 42 associated with the name entered in that field 1110 by the user 12. The system then correlates the event information 42 associated with the name entered by the user 12, with event-related agency information 40 to determine if the name entered in the field 1110 by the user 12 fails to meet the statutory requirements as a result of some disqualifying event contained in event information 42 associated with the name entered in the field 1110 by the user 12 (e.g., Contract with a bankrupt company, incapacitated person, minor, felon, etc.). Combining background checks with forms 46 to identify correlation that a user 12 may not have known or otherwise considered provides a means for the user 12 to automatically verify an entry typed into a field 1110 on a form 60 used to generate document 46.

An alternative embodiment may be configured to automatically locate the registered agent of an entity in response to a user 12 populating a numbered field 1110 on a form 60 correlating to entity names. A user 12 may begin to enter the entity name, and the system 10 may correlate the numbered field 1110 on the form 60 with event information 42 or agency information 40 to determine if a user's 12 entry contains an error. The system 10 may also make suggestions for a user 12 based on correlations with the numbered field 1110 on a form 60, and agency information 40 and event information 42 associated with a user 12. A user 12 types of the name of registered entity into the numbered field 1110 on a form 60 that must contain a business entity's name or registered DBA (“Doing business as”). The system 10 queries the event information databases 34 to correlate a user's 12 entry with event information 42 associated with the business entity entered in the numbered field 1110 by the user 12. If a user's 12 entry matches the correlating event information 42, the system 10 automatically populates any remaining fields 1110 on the form 60 that correlates with the event information 42 collected for particular field 1110 on a form 60 that the user 12 entered a business entity's name. If a user 12 misspells a registered company's name, the system 10 notifies a user 12 to correct a user 12 error to reflect a correct entry according to event information 42 available to the system 10.

An alternative embodiment may allow a user 12 to generate a will 132 based on a form 60 that is relevant to a user 12. Once a user 12 logs in through a secured third-party provider login 26, like in the example above where a petition for expunction, as shown in FIGS. 12A-12E, was generated, the system 10 will identify a user 12 and query event information databases 34 for all property interests that match a user's 12 personal information 30. The system 10 automatically populates relevant fields 1110 on will form 60 templates with the event information 42 associated with a user 12.

The system 10 may suggest that a user 12 include certain assets identified by the system 10 to eliminate the need for a user 12 to enter the data. The system 10 may also suggest devisees based on event records 62 sourced from event information databases 34 and the information received from the secured third-party service provider databases 28. The system 10 may also provide notice to devisees in a will 132 by identifying a user's devisees by name in a will 132 and sending the devisees a notification 52 through the notification system 59 based on the contact information available to the system 10 from the event information databases 34, third-party service provider databases 28, and/or the user 12.

An alternative embodiment of the system 10 may send search queries across the internet to locate websites that possess event information 42 associated with a user 12. A user 12 may then choose to respond or have the system 10 respond automatically with an automatically generated document 46. The document 46 may be used to provide the owner of the website with notice that the possession of the event information 42 correlates with a violation of agency information 40 requirements, and that a beneficial document 46 has been generated for a user 12. The system 10 may deliver the document 46 by e-mail or allow a user 12 to print 68 and mail the letters manually. This service allows users 12 of the system 10 to monitor the presence of event information 42 associated with a user 12 across the Internet. A user 12 now has the benefit of responding to websites that possess event information 42 associated with a user 12 that a user 12 may want to be aware of and/or request the event information 42 associated with the user 12 be removed.

An alternative embodiment may call out to the event information databases 34 to create or edit entries in a user 12, organization, or lawyer or law firm's calendar. The system 10 calls out to public record databases to collect event information 42 associated with a court's docket or calendar that is also associated with a user 12. The system 10 will call out to public record databases to collect event-related agency information 40, like the Federal (or State) Rules of Civil and/or Criminal Procedure and format the information to be expressed in the form 60 of an algorithm. The event information 42 associated with a user 12 is given a numerical value and plugged into an algorithm of event-related agency information 40 to identify correlations between the various information that may be useful or beneficial to a user 12. For example, the system 10 may notify a user 12 by sending a notification 52 through the notification system 59. Notifications 52 could alert a user 12 about an approaching deadline for filing documents 46, in accordance with court filing rules 128, responding to a discovery request, or for a trial appearance date based on the event information 42 associated with a user 12.

An alternative embodiment may automatically generate a deed or land sale contract based on the event information 42 associated with the registered owner in the public records databases. The system 10 may be utilized to generate title opinions and other documents 46 as well. The event-related agency information 40 would include relevant statutes with respect to real property and determining the owner of, and/or issues associated with the transferring of ownership, to title in real property. The system 10 would source the information and generate the documents 46 similar to the processes outlined above for generating the petition for expunction. The system 10 may be configured to include this event-related agency information 40 expressed in the form 60 of an algorithm. The event information 42 may be assigned numerical values by the acquisition system 32 and/or the formatting system 74 for the relevant event information 42 associated with a user 12 and/or property. The algorithm may be configured to determine if any title issues exist based on the relationship of the event information 42 with the event-related agency information 40. The system 10 would reach this determination based on the result of the algorithm after the numerical values assigned to the variables corresponding to the event information 42 are included in the algorithm expressing the event-related agency information 40. The system 10 could then populate a form 60 using the event information 42 to generate a document 46 for a user 12. The document 46 may be a title opinion or other document 46 of interest to a user 12. A user 12 may insert new forms 60 and set new rules for the system's formatting system 74 to consider when generating documents 46.

An alternative embodiment may utilize the same system 10 design as in FIG. 1A, using the secured third-party service provider login 26 for authenticating a user 12 at login, the system 10 may then call out by secure connection to the API of the same secured third-party service provider's databases 28, or a different secured third-party service provider's databases 28, to add increased functionality and additional services 64 by taking advantage of cloud-based platforms offered by the secured third-party service provider. For example, Wolfram Alpha allows developers to call out to Wolfram Alpha's API in order to create new products and services that leverage computable knowledge of information and to enhance existing web properties of the system 10. The system 10 uses this increased functionality from Wolfram Alpha to analyze trends in case law 142 event information 42 or changes in event-related agency information 40. The increased analytics 144 will be tied to trigger a notification 52 to a user 12 in the event that a user 12 is interested in learning more about a particular statute found in the agency information 40 and how that statute relates to event information 42 (e.g., like the number of arrests as a result of the statute). A user 12 may query the system 10 to provide analytics that may be helpful in analyzing the public records information that may be of particular interest to a user 12. If a user 12 is an attorney, a user 12 may benefit from analysis that compares agency information 40 across different states or jurisdictions to determine the percentage of cases that were successful under a particular statute compared with the statute of the other jurisdiction. The system 10 may also save in aggregate user 12 personal information 30 as a dataset that can be compared with public records information.

An alternative embodiment may call out to the public records information databases for public records information, including event information 42 associated with a user 12 that can be plugged into an algorithm or series of algorithms that expresses relevant event-related and/or document-related agency information 40 in order to make inferences or conclusions based on the result of the algorithm after the event information 42, which may assigned values by the acquisition system 32, is used as the variables in the algorithm(s). The system 10 could identity what form 60 or document 46 may be needed, the likelihood of success based on the results of others found in event information 42 associated with other individuals, and to determine what information may require query responses from a user 12.

An alternative embodiment may call out to third-party service provider databases 28 to collect personal information 28 associated with a user 12, or user(s), that may also correlate to a particular document 46. Information from personal social media accounts, e-mail accounts, and other websites that gather 12 personal information 30 is gathered would provide the information necessary to both identify beneficial documents 46 for a user 12, and then populate the documents 46 with the personal information 30. The data mining techniques, and other techniques, may be employed to send search queries to the third-party service provider databases 28 that a user 12 identifies as having an account with or by identifying third-party service providers that a user 12 has an account to login 26 with. The system 10 may also make suggestions to a user 12 of websites that may contain information that is beneficial to the automatic generation of a particular document 46 or area of documents 46. Information from social media, e-mail, health care providers 142, educational institutions, and other third-party service providers may provide valuable information to a user 12. The system 10 may collect this information associated with a user 12, format the information into data fields 616 similar to the manner described in the above examples, such as in FIG. 1A, and assign numerical values to the information based on an algorithm or series of algorithms that represent agency information 40, or to make any other inference or determination based on information, and then to identify, suggest, and/or provide documents 46 and solutions for a user 12 that correlate to the information or that are based on the inferences and determinations reached on the analysis of the information with respect to the results of the algorithm. If the system 10 identifies a correlating document 46 to the information, the system 10 may automatically generate the documents 46 and use the information associated with a user 12 to populate the documents 46. Information available with different third-party service providers that provide different services, or are otherwise associated, with a user 12 each may possess information that collectively would allow for determinations or inferences to be reached and also documents 46 to be generated or suggested by the system 10 for a user 12. A user 12 may automatically generate a will 132 document 46 that contains all of a user's 12 assets and family members by sourcing event information 42 and personal information 30 associated with a user 12 and correlating that information to numbered fields 1110 on a form 60 designed to generate a will 132 document. The system 10 may locate assets by connecting to a user's 12 third-party service provider, for example mint.com, to determine the assets that a user 12 may be to include in a will. The system 10 may then send search queries for event information 42 that may provide the system 10 with information on possible family relationships associated with a user 12 as well as additional assets as well as geographic information associated with a user 12. The system 10 may also source particular personal information 30 containing information on the interactions of a user 12 with the other social media websites and call out search queries, with a user's 12 permission, to these secured third-party service provider databases 28 to collect the personal information 30 that will identify on the extent of a user's 12 relationships and interactions with other individuals to determine how, and possibly to whom, a user 12 interacts with, and may want to consider including in a user's 12 will. This information may be correlated with event-related agency information 40 associated with a numbered field 1110 on a form 60 designed to generate a will document 46 for a user 12. The system 10 may then populate the form 60 with the personal information 30 sourced from the third-party service providers and event information 42 in order to generate a will document 132. The system 10 may determine the possible recipients a user 12 may wish to include in a will 132 based on the relationships interactions of a user 12 with other individuals. The system 10 may also correlate the personal information 30 associated with a user 12, including geographic information associated with a user 12 and/or a user's assets, with the document-related agency information 40 to suggest strategies or documents 46 to a user 12 that may benefit a user 12, by, for example, reducing a user's 12 tax consequence or the tax consequence of a user's 12 devisee(s). A user 12 may edit a document 46 or populate fields 1110 on the document 46 that the system 10 was not able to populate automatically.

Another alternative embodiment may use social media, web history, and other digital records from secure third-party service provider databases to assist in document 46 generation as well as discovery assistance. The invention could use an algorithm designed to identify responsive data and a user 12 could allow the system 10 permission to access a user's 12 personal digital records, possibly on their personal computer 16 or mobile device 18, in order to aid with discovery or to identify digital information in advance of litigation by correlating information in personal digital records of a user 12 and agency information, including event-related agency information 40. The envisioned embodiment could determine responsive discovery material in advance of litigation as an effort to avoid litigation. The algorithm can also be adjusted to account for different industries and lawsuit types as well as to accommodate for current litigation.

While the foregoing written description of the current disclosure enables one of ordinary skill to make and use what is considered presently to be the best mode thereof, those of ordinary skill will understand and appreciate the existence of variations, combinations, and equivalents of the specific embodiment, method, and examples herein. The invention should therefore not be limited by the above-described embodiment, method, and examples, but by all embodiments and methods within the scope and spirit of the invention.

Specific details are given in the above description to provide a thorough understanding of various preferred embodiments. However, it is understood that these and other embodiments may be practiced without these specific details. For example, processes may be shown in diagrams in order not to obscure the embodiments in unnecessary detail. In other instances, well-known processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

Implementation of the techniques, blocks, steps, and means described above may be done in various ways. For example, these techniques, blocks, steps, and means may be implemented in hardware, software, or a combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, or other electronic units designed to perform the functions described above, and/or a combination thereof

Also, it is noted that the embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be rearranged. A process is terminated when its operations are completed but could have many additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination corresponds to a return of the function to the calling function or the main function.

Embodiments of the invention may involve middleware and/or other software implementations; the methodologies may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions may be used in implementing the methodologies described herein. For example, software codes may be stored in a memory. Memory may be implemented within the processor or external to the processor and may be downloadable through an internet connection service. As used herein, the term “memory” refers to any type of long term, short term, volatile, nonvolatile, or other storage medium and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.

Moreover, as disclosed herein, the term “storage medium” may represent one or more memories for storing data, including read-only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine-readable mediums for storing information. The term “machine-readable medium” includes but is not limited to portable or fixed storage devices, optical storage devices, wireless channels, and/or various other storage mediums capable of storing that contain or carry instruction(s) and/or data.

Furthermore, embodiments may be implemented by hardware, software, scripting languages, firmware, middleware, microcode, hardware description languages, and/or any combination thereof. When implemented in software, firmware, middleware, scripting language, and/or microcode, the program code or code segments to perform the necessary tasks may be stored in a machine-readable medium such as a storage medium. A code segment or machine-executable instruction may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a script, a class, or any combination of instructions, data structures, and/or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, and/or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc.

While the principles of the disclosure have been described above in connection with specific methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the disclosure. Whether now known or later discovered, there are countless other alternatives, variations and modifications of the many features of the various described and illustrated embodiments, both in the process and in the system characteristics, that will be evident to those of skill in the art after careful and discerning review of the foregoing descriptions, particularly if they are also able to review all of the various systems and methods that have been tried in the public domain or otherwise described in the prior art. All such alternatives, variations and modifications are contemplated to fall within the scope of the present invention.

Although the present invention has been described in terms of the foregoing preferred and alternative embodiments, these descriptions and embodiments have been provided by way of explanation of examples only, in order to facilitate understanding of the present invention. As such, the descriptions and embodiments are not to be construed as limiting the present invention, the scope of which is limited only by the claims of this and any related patent applications and any amendments thereto.

Other embodiments will be evident to one of ordinary skill in the art is illustrated in the attached Exhibit A incorporated herein by reference. 

We claim:
 1. A system for automatically generating a formatted document, the system comprising: a) a computer system comprising: 1) an acquisition system being in secure network communication with a plurality of third-party databases, the acquisition system being configured and adapted to acquire information related to a user of the system from one or more databases in the plurality of third-party databases; 2) a formatting system being configured and adapted to format the acquired information related to the user of the system; 3) a system database being configured to store and organize the acquired information, the system database being adapted to provide a data table having a plurality of data fields; and 4) a forms database being adapted to store a plurality of document templates; b) wherein the acquired information related to the user comprises: 1) personal information related to the user; 2) event information, wherein the event information is related to an event associated with the user; and 3) agency information, wherein the agency information may be acquired from one or more agencies, and wherein at least a portion of the agency information is related to the event associated with the user; c) wherein the acquisition system is adapted to populate the data fields in the data table with the formatted acquired information; d) the computer system being adapted to: 1) correlate the agency information related to the event with the event information; 2) based at least in part on the correlation, select an appropriate document template in the plurality of document templates; and 3) populate fields on the selected appropriate document template for generating the formatted document.
 2. The system of claim 1, wherein the acquisition system is further configured to call out to an Application Programming Interface (API) of a third-party service provider for authenticating the user.
 3. The system of claim 1, wherein the event information includes relevant date information related to the event, arrest records, case status, charge type, misdemeanor class or felony degree, related charges, case disposition records, and appeal status.
 4. The system of claim 1, wherein the agency information associated with the event includes criminal code stats, codified rules of criminal procedure, internal agency policies, costs of filing documents, and agency contact information.
 5. The system of claim 1, wherein the computer system is further adapted to determine, based on the correlation, whether the event information associated with the user meets statutory requirements for expunction.
 6. The system of claim 5, wherein the formatted document is a petition for expunction.
 7. The system of claim 6, wherein the computer system is configured to provide electronic filing options for filing the petition for expunction with an appropriate agency.
 8. The system of claim 1, wherein the formatted document relates to a request to restrict access to at least a portion of the event information.
 9. The system of claim 1, wherein the formatted document relates to a request to seal records related to the event information.
 10. A method for automatically generating a formatted document, the method comprising: a) determining event information related to an event associated with a user by sending one or more queries to one or more third-party databases having event information; b) determining agency information related to the event associated with the user by sending one or more queries to one or more third-party databases having agency information; c) correlating the event information associated with the user with the agency information related to the event; d) selecting a document template from a forms database, wherein the document template is related to the event information associated with the user, wherein the document template includes a plurality of open fields; e) generating the formatted document by populating the plurality of open fields on the document template that correlate with the event, the agency information, and personal information associated with the user.
 11. The method of claim 10, further comprising authenticating the user, wherein the authentication comprises calling out to an Application Programming Interface (API) associated with a third-party service provider and receiving personal information associated with the user.
 12. The method of claim 10, wherein the event information includes relevant data information related to the event, arrest records, case status, charge type, misdemeanor class or felony degree, related charges, case disposition records, and appeal status.
 13. The method of claim 10, wherein the agency information associated with the event includes criminal code status, codified rules of criminal procedure, internal agency policies, costs of filing documents, and agency contact information.
 14. The method of claim 10, further comprising determining, based at least in part on the correlation of the event information associated with the user with the agency information related to the event, whether the event information associated with the user meets statutory requirements for expunction.
 15. The method of claim 14, wherein the formatted document is a petition for expunction.
 16. The method of claim 15, further comprising providing electronic filing options for filing the petition for expunction with an appropriate agency.
 17. The method of claim 10, wherein the formatted document relates to a request to restrict access to at least a portion of the event information.
 18. The method of claim 10, wherein the formatted document relates to a request to seal records related to the event information. 